Group power control for a secondary cell

ABSTRACT

A wireless device may receive message(s) comprising configuration parameters for cells comprising a primary cell and a secondary cell. The configuration parameters may comprise: a transmit power control (TPC) radio network temporary identifier (RNTI), a primary TPC index for a first physical uplink shared channel (PUSCH) of the primary cell, a secondary TPC index for a second PUSCH of the secondary cell, and periodic resource allocation configuration parameters configuring a periodic resource allocation for the secondary cell. A first downlink control information (DCI) may be received indicating activation of the periodic resource allocation. A common search space for a second DCI associated with the TPC RNTI may be monitored. The second DCI may comprise a sequence of TPC commands. The secondary TPC index may identify a TPC command in the sequence. Transport blocks may be transmitted by employing transmission parameter(s) in the first DCI and the TPC command.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/372,120, filed Aug. 8, 2016, which is hereby incorporated byreference in its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers in a carrier group as per an aspect of anembodiment of the present disclosure.

FIG. 3 is an example diagram depicting OFDM radio resources as per anaspect of an embodiment of the present disclosure.

FIG. 4 is an example block diagram of a base station and a wirelessdevice as per an aspect of an embodiment of the present disclosure.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 6 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present disclosure.

FIG. 7 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present disclosure.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure.

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure.

FIG. 10 is an example diagram depicting Activation/Deactivation MACcontrol elements as per an aspect of an embodiment of the presentdisclosure.

FIG. 11 is an example diagram depicting example subframe offset valuesas per an aspect of an embodiment of the present disclosure.

FIG. 12 is an example diagram depicting example uplink SPS activationand release as per an aspect of an embodiment of the present disclosure.

FIG. 13 is an example power control command mapping as per an aspect ofan embodiment of the present disclosure.

FIG. 14 is an example power control command mapping as per an aspect ofan embodiment of the present disclosure.

FIG. 15 is an example mapping between DCI format and search space as peran aspect of an embodiment of the present disclosure.

FIG. 16 is an example mapping between DCI format and search space as peran aspect of an embodiment of the present disclosure.

FIG. 17 is an example mapping between DCI format and search space as peran aspect of an embodiment of the present disclosure.

FIG. 18 is an example procedure for group power control as per an aspectof an embodiment of the present disclosure.

FIG. 19 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

FIG. 20 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present disclosure enable operation ofcarrier aggregation. Embodiments of the technology disclosed herein maybe employed in the technical field of multicarrier communicationsystems.

The following Acronyms are used throughout the present disclosure:

ASIC application-specific integrated circuit

BPSK binary phase shift keying

CA carrier aggregation

CSI channel state information

CDMA code division multiple access

CSS common search space

CPLD complex programmable logic devices

CC component carrier

DL downlink

DCI downlink control information

DC dual connectivity

EPC evolved packet core

E-UTRAN evolved-universal terrestrial radio access network

FPGA field programmable gate arrays

FDD frequency division multiplexing

HDL hardware description languages

HARQ hybrid automatic repeat request

IE information element

LAA licensed assisted access

LTE long term evolution

MCG master cell group

MeNB master evolved node B

MIB master information block

MAC media access control

MAC media access control

MME mobility management entity

NAS non-access stratum

OFDM orthogonal frequency division multiplexing

PDCP packet data convergence protocol

PDU packet data unit

PHY physical

PDCCH physical downlink control channel

PHICH physical HARQ indicator channel

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

PCell primary cell

PCell primary cell

PCC primary component carrier

PSCell primary secondary cell

pTAG primary timing advance group

QAM quadrature amplitude modulation

QPSK quadrature phase shift keying

RBG Resource Block Groups

RLC radio link control

RRC radio resource control

RA random access

RB resource blocks

SCC secondary component carrier

SCell secondary cell

Scell secondary cells

SCG secondary cell group

SeNB secondary evolved node B

sTAGs secondary timing advance group

SDU service data unit

S-GW serving gateway

SRB signaling radio bearer

SC-OFDM single carrier-OFDM

SFN system frame number

SIB system information block

TAI tracking area identifier

TAT time alignment timer

TDD time division duplexing

TDMA time division multiple access

TA timing advance

TAG timing advance group

TB transport block

UL uplink

UE user equipment

VHDL VHSIC hardware description language

Example embodiments of the disclosure may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CDMA, OFDM,TDMA, Wavelet technologies, and/or the like. Hybrid transmissionmechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.Various modulation schemes may be applied for signal transmission in thephysical layer. Examples of modulation schemes include, but are notlimited to: phase, amplitude, code, a combination of these, and/or thelike. An example radio transmission method may implement QAM using BPSK,QPSK, 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, arrow(s) in the diagram may depict a subcarrier in amulticarrier OFDM system. The OFDM system may use technology such asOFDM technology, DFTS-OFDM, SC-OFDM technology, or the like. Forexample, arrow 101 shows a subcarrier transmitting information symbols.FIG. 1 is for illustration purposes, and a typical multicarrier OFDMsystem may include more subcarriers in a carrier. For example, thenumber of subcarriers in a carrier may be in the range of 10 to 10,000subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmissionband. As illustrated in FIG. 1, guard band 106 is between subcarriers103 and subcarriers 104. The example set of subcarriers A 102 includessubcarriers 103 and subcarriers 104. FIG. 1 also illustrates an exampleset of subcarriers B 105. As illustrated, there is no guard band betweenany two subcarriers in the example set of subcarriers B 105. Carriers ina multicarrier OFDM communication system may be contiguous carriers,non-contiguous carriers, or a combination of both contiguous andnon-contiguous carriers.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers as per an aspect of an embodiment of the presentdisclosure. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 10 carriers. Carrier A 204and carrier B 205 may have the same or different timing structures.Although FIG. 2 shows two synchronized carriers, carrier A 204 andcarrier B 205 may or may not be synchronized with each other. Differentradio frame structures may be supported for FDD and TDD duplexmechanisms. FIG. 2 shows an example FDD frame timing. Downlink anduplink transmissions may be organized into radio frames 201. In thisexample, the radio frame duration is 10 msec. Other frame durations, forexample, in the range of 1 to 100 msec may also be supported. In thisexample, each 10 ms radio frame 201 may be divided into ten equallysized subframes 202. Other subframe durations such as 0.5 msec, 1 msec,2 msec, and 5 msec may also be supported. Subframe(s) may consist of twoor more slots (for example, slots 206 and 207). For the example of FDD,10 subframes may be available for downlink transmission and 10 subframesmay be available for uplink transmissions in each 10 ms interval. Uplinkand downlink transmissions may be separated in the frequency domain.Slot(s) may include a plurality of OFDM symbols 203. The number of OFDMsymbols 203 in a slot 206 may depend on the cyclic prefix length andsubcarrier spacing.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure. The resource grid structure intime 304 and frequency 305 is illustrated in FIG. 3. The quantity ofdownlink subcarriers or RBs (in this example 6 to 100 RBs) may depend,at least in part, on the downlink transmission bandwidth 306 configuredin the cell. The smallest radio resource unit may be called a resourceelement (e.g. 301). Resource elements may be grouped into resourceblocks (e.g. 302). Resource blocks may be grouped into larger radioresources called Resource Block Groups (RBG) (e.g. 303). The transmittedsignal in slot 206 may be described by one or several resource grids ofa plurality of subcarriers and a plurality of OFDM symbols. Resourceblocks may be used to describe the mapping of certain physical channelsto resource elements. Other pre-defined groupings of physical resourceelements may be implemented in the system depending on the radiotechnology. For example, 24 subcarriers may be grouped as a radio blockfor a duration of 5 msec. In an illustrative example, a resource blockmay correspond to one slot in the time domain and 180 kHz in thefrequency domain (for 15 KHz subcarrier bandwidth and 12 subcarriers).

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 5A shows an example uplink physicalchannel. The baseband signal representing the physical uplink sharedchannel may perform the following processes. These functions areillustrated as examples and it is anticipated that other mechanisms maybe implemented in various embodiments. The functions may comprisescrambling, modulation of scrambled bits to generate complex-valuedsymbols, mapping of the complex-valued modulation symbols onto one orseveral transmission layers, transform precoding to generatecomplex-valued symbols, precoding of the complex-valued symbols, mappingof precoded complex-valued symbols to resource elements, generation ofcomplex-valued time-domain DFTS-OFDM/SC-FDMA signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued DFTS-OFDM/SC-FDMA baseband signal for each antenna portand/or the complex-valued PRACH baseband signal is shown in FIG. 5B.Filtering may be employed prior to transmission.

An example structure for Downlink Transmissions is shown in FIG. 5C. Thebaseband signal representing a downlink physical channel may perform thefollowing processes. These functions are illustrated as examples and itis anticipated that other mechanisms may be implemented in variousembodiments. The functions include scrambling of coded bits in each ofthe codewords to be transmitted on a physical channel; modulation ofscrambled bits to generate complex-valued modulation symbols; mapping ofthe complex-valued modulation symbols onto one or several transmissionlayers; precoding of the complex-valued modulation symbols on each layerfor transmission on the antenna ports; mapping of complex-valuedmodulation symbols for each antenna port to resource elements;generation of complex-valued time-domain OFDM signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for each antenna port is shown inFIG. 5D. Filtering may be employed prior to transmission.

FIG. 4 is an example block diagram of a base station 401 and a wirelessdevice 406, as per an aspect of an embodiment of the present disclosure.A communication network 400 may include at least one base station 401and at least one wireless device 406. The base station 401 may includeat least one communication interface 402, at least one processor 403,and at least one set of program code instructions 405 stored innon-transitory memory 404 and executable by the at least one processor403. The wireless device 406 may include at least one communicationinterface 407, at least one processor 408, and at least one set ofprogram code instructions 410 stored in non-transitory memory 409 andexecutable by the at least one processor 408. Communication interface402 in base station 401 may be configured to engage in communicationwith communication interface 407 in wireless device 406 via acommunication path that includes at least one wireless link 411.Wireless link 411 may be a bi-directional link. Communication interface407 in wireless device 406 may also be configured to engage in acommunication with communication interface 402 in base station 401. Basestation 401 and wireless device 406 may be configured to send andreceive data over wireless link 411 using multiple frequency carriers.According to aspects of an embodiments, transceiver(s) may be employed.A transceiver is a device that includes both a transmitter and receiver.Transceivers may be employed in devices such as wireless devices, basestations, relay nodes, and/or the like. Example embodiments for radiotechnology implemented in communication interface 402, 407 and wirelesslink 411 are illustrated are FIG. 1, FIG. 2, FIG. 3, FIG. 5, andassociated text.

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics inthe device, whether the device is in an operational or non-operationalstate.

According to various aspects of an embodiment, an LTE network mayinclude a multitude of base stations, providing a user planePDCP/RLC/MAC/PHY and control plane (RRC) protocol terminations towardsthe wireless device. The base station(s) may be interconnected withother base station(s) (for example, interconnected employing an X2interface). Base stations may also be connected employing, for example,an S1 interface to an EPC. For example, base stations may beinterconnected to the MME employing the S1-MME interface and to the S-G)employing the S1-U interface. The S1 interface may support amany-to-many relation between MMEs/Serving Gateways and base stations. Abase station may include many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may include many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At RRC connectionestablishment/re-establishment/handover, one serving cell may providethe NAS (non-access stratum) mobility information (e.g. TAI), and at RRCconnection re-establishment/handover, one serving cell may provide thesecurity input. This cell may be referred to as the Primary Cell(PCell). In the downlink, the carrier corresponding to the PCell may bethe Downlink Primary Component Carrier (DL PCC), while in the uplink,the carrier corresponding to the PCell may be the Uplink PrimaryComponent Carrier (UL PCC). Depending on wireless device capabilities,Secondary Cells (SCells) may be configured to form together with thePCell a set of serving cells. In the downlink, the carrier correspondingto an SCell may be a Downlink Secondary Component Carrier (DL SCC),while in the uplink, it may be an Uplink Secondary Component Carrier (ULSCC). An SCell may or may not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or Cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context it is used). In the specification, cell ID maybe equally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, when thespecification refers to a first physical cell ID for a first downlinkcarrier, the specification may mean the first physical cell ID is for acell comprising the first downlink carrier. The same concept may apply,for example, to carrier activation. When the specification indicatesthat a first carrier is activated, the specification may also mean thatthe cell comprising the first carrier is activated.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, traffic load, initial systemset up, packet sizes, traffic characteristics, a combination of theabove, and/or the like. When the one or more criteria are met, variousexample embodiments may be applied. Therefore, it may be possible toimplement example embodiments that selectively implement disclosedprotocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices may support multiple technologies, and/or multiple releases ofthe same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE release with agiven capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of wireless devices in a coveragearea that may not comply with the disclosed methods, for example,because those wireless devices perform based on older releases of LTEtechnology.

FIG. 6 and FIG. 7 are example diagrams for protocol structure with CAand DC as per an aspect of an embodiment of the present disclosure.E-UTRAN may support Dual Connectivity (DC) operation whereby a multipleRX/TX UE in RRC_CONNECTED may be configured to utilize radio resourcesprovided by two schedulers located in two eNBs connected via a non-idealbackhaul over the X2 interface. eNBs involved in DC for a certain UE mayassume two different roles: an eNB may either act as an MeNB or as anSeNB. In DC a UE may be connected to one MeNB and one SeNB. Mechanismsimplemented in DC may be extended to cover more than two eNBs. FIG. 7illustrates one example structure for the UE side MAC entities when aMaster Cell Group (MCG) and a Secondary Cell Group (SCG) are configured,and it may not restrict implementation. Media Broadcast MulticastService (MBMS) reception is not shown in this figure for simplicity.

In DC, the radio protocol architecture that a particular bearer uses maydepend on how the bearer is setup. Three alternatives may exist, an MCGbearer, an SCG bearer and a split bearer as shown in FIG. 6. RRC may belocated in MeNB and SRBs may be configured as a MCG bearer type and mayuse the radio resources of the MeNB. DC may also be described as havingat least one bearer configured to use radio resources provided by theSeNB. DC may or may not be configured/implemented in example embodimentsof the disclosure.

In the case of DC, the UE may be configured with two MAC entities: oneMAC entity for MeNB, and one MAC entity for SeNB. In DC, the configuredset of serving cells for a UE may comprise two subsets: the Master CellGroup (MCG) containing the serving cells of the MeNB, and the SecondaryCell Group (SCG) containing the serving cells of the SeNB. For a SCG,one or more of the following may be applied. At least one cell in theSCG may have a configured UL CC and one of them, named PSCell (or PCellof SCG, or sometimes called PCell), may be configured with PUCCHresources. When the SCG is configured, there may be at least one SCGbearer or one Split bearer. Upon detection of a physical layer problemor a random access problem on a PSCell, or the maximum number of RLCretransmissions has been reached associated with the SCG, or upondetection of an access problem on a PSCell during a SCG addition or aSCG change: a RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of the SCG may be stopped, anda MeNB may be informed by the UE of a SCG failure type. For splitbearer, the DL data transfer over the MeNB may be maintained. The RLC AMbearer may be configured for the split bearer. Like a PCell, a PSCellmay not be de-activated. A PSCell may be changed with a SCG change (forexample, with a security key change and a RACH procedure), and/orneither a direct bearer type change between a Split bearer and a SCGbearer nor simultaneous configuration of a SCG and a Split bearer may besupported.

With respect to the interaction between a MeNB and a SeNB, one or moreof the following principles may be applied. The MeNB may maintain theRRM measurement configuration of the UE and may, (for example, based onreceived measurement reports or traffic conditions or bearer types),decide to ask a SeNB to provide additional resources (serving cells) fora UE. Upon receiving a request from the MeNB, a SeNB may create acontainer that may result in the configuration of additional servingcells for the UE (or decide that it has no resource available to do so).For UE capability coordination, the MeNB may provide (part of) the ASconfiguration and the UE capabilities to the SeNB. The MeNB and the SeNBmay exchange information about a UE configuration by employing RRCcontainers (inter-node messages) carried in X2 messages. The SeNB mayinitiate a reconfiguration of its existing serving cells (for example, aPUCCH towards the SeNB). The SeNB may decide which cell is the PSCellwithin the SCG. The MeNB may not change the content of the RRCconfiguration provided by the SeNB. In the case of a SCG addition and aSCG SCell addition, the MeNB may provide the latest measurement resultsfor the SCG cell(s). Both a MeNB and a SeNB may know the SFN andsubframe offset of each other by OAM, (for example, for the purpose ofDRX alignment and identification of a measurement gap). In an example,when adding a new SCG SCell, dedicated RRC signaling may be used forsending required system information of the cell as for CA, except forthe SFN acquired from a MIB of the PSCell of a SCG.

In an example, serving cells may be grouped in a TA group (TAG). Servingcells in one TAG may use the same timing reference. For a given TAG,user equipment (UE) may use at least one downlink carrier as a timingreference. For a given TAG, a UE may synchronize uplink subframe andframe transmission timing of uplink carriers belonging to the same TAG.In an example, serving cells having an uplink to which the same TAapplies may correspond to serving cells hosted by the same receiver. AUE supporting multiple TAs may support two or more TA groups. One TAgroup may contain the PCell and may be called a primary TAG (pTAG). In amultiple TAG configuration, at least one TA group may not contain thePCell and may be called a secondary TAG (sTAG). In an example, carrierswithin the same TA group may use the same TA value and/or the sametiming reference. When DC is configured, cells belonging to a cell group(MCG or SCG) may be grouped into multiple TAGs including a pTAG and oneor more sTAGs.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure. In Example 1, pTAG comprises aPCell, and an sTAG comprises SCell1. In Example 2, a pTAG comprises aPCell and SCell1, and an sTAG comprises SCell2 and SCell3. In Example 3,pTAG comprises PCell and SCell1, and an sTAG1 includes SCell2 andSCell3, and sTAG2 comprises SCell4. Up to four TAGs may be supported ina cell group (MCG or SCG) and other example TAG configurations may alsobe provided. In various examples in this disclosure, example mechanismsare described for a pTAG and an sTAG. Some of the example mechanisms maybe applied to configurations with multiple sTAGs.

In an example, an eNB may initiate an RA procedure via a PDCCH order foran activated SCell. This PDCCH order may be sent on a scheduling cell ofthis SCell. When cross carrier scheduling is configured for a cell, thescheduling cell may be different than the cell that is employed forpreamble transmission, and the PDCCH order may include an SCell index.At least a non-contention based RA procedure may be supported forSCell(s) assigned to sTAG(s).

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure. An eNB transmits an activation command 600 to activate anSCell. A preamble 602 (Msg1) may be sent by a UE in response to a PDCCHorder 601 on an SCell belonging to an sTAG. In an example embodiment,preamble transmission for SCells may be controlled by the network usingPDCCH format 1A. Msg2 message 603 (RAR: random access response) inresponse to the preamble transmission on the SCell may be addressed toRA-RNTI in a PCell common search space (CSS). Uplink packets 604 may betransmitted on the SCell in which the preamble was transmitted.

According to an embodiment, initial timing alignment may be achievedthrough a random access procedure. This may involve a UE transmitting arandom access preamble and an eNB responding with an initial TA commandNTA (amount of timing advance) within a random access response window.The start of the random access preamble may be aligned with the start ofa corresponding uplink subframe at the UE assuming NTA=0. The eNB mayestimate the uplink timing from the random access preamble transmittedby the UE. The TA command may be derived by the eNB based on theestimation of the difference between the desired UL timing and theactual UL timing. The UE may determine the initial uplink transmissiontiming relative to the corresponding downlink of the sTAG on which thepreamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. According to variousaspects of an embodiment, when an eNB performs an SCell additionconfiguration, the related TAG configuration may be configured for theSCell. In an example embodiment, an eNB may modify the TAG configurationof an SCell by removing (releasing) the SCell and adding (configuring) anew SCell (with the same physical cell ID and frequency) with an updatedTAG ID. The new SCell with the updated TAG ID may initially be inactivesubsequent to being assigned the updated TAG ID. The eNB may activatethe updated new SCell and start scheduling packets on the activatedSCell. In an example implementation, it may not be possible to changethe TAG associated with an SCell, but rather, the SCell may need to beremoved and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, (for example, at least one RRC reconfigurationmessage), may be send to the UE to reconfigure TAG configurations byreleasing the SCell and then configuring the SCell as a part of thepTAG. When an SCell is added/configured without a TAG index, the SCellmay be explicitly assigned to the pTAG. The PCell may not change its TAgroup and may be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (for example, to establish, modify and/orrelease RBs, to perform handover, to setup, modify, and/or releasemeasurements, to add, modify, and/or release SCells). If the receivedRRC Connection Reconfiguration message includes the sCellToReleaseList,the UE may perform an SCell release. If the received RRC ConnectionReconfiguration message includes the sCellToAddModList, the UE mayperform SCell additions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH may only be transmitted onthe PCell (PSCell) to an eNB. In LTE-Release 12 and earlier, a UE maytransmit PUCCH information on one cell (PCell or PSCell) to a given eNB.

As the number of CA capable UEs and also the number of aggregatedcarriers increase, the number of PUCCHs and also the PUCCH payload sizemay increase. Accommodating the PUCCH transmissions on the PCell maylead to a high PUCCH load on the PCell. A PUCCH on an SCell may beintroduced to offload the PUCCH resource from the PCell. More than onePUCCH may be configured for example, a PUCCH on a PCell and anotherPUCCH on an SCell. In the example embodiments, one, two or more cellsmay be configured with PUCCH resources for transmitting CSI/ACK/NACK toa base station. Cells may be grouped into multiple PUCCH groups, and oneor more cell within a group may be configured with a PUCCH. In anexample configuration, one SCell may belong to one PUCCH group. SCellswith a configured PUCCH transmitted to a base station may be called aPUCCH SCell, and a cell group with a common PUCCH resource transmittedto the same base station may be called a PUCCH group.

In an example embodiment, a MAC entity may have a configurable timertimeAlignmentTimer per TAG. The timeAlignmentTimer may be used tocontrol how long the MAC entity considers the Serving Cells belonging tothe associated TAG to be uplink time aligned. The MAC entity may, when aTiming Advance Command MAC control element is received, apply the TimingAdvance Command for the indicated TAG; start or restart thetimeAlignmentTimer associated with the indicated TAG. The MAC entitymay, when a Timing Advance Command is received in a Random AccessResponse message for a serving cell belonging to a TAG and/orif theRandom Access Preamble was not selected by the MAC entity, apply theTiming Advance Command for this TAG and start or restart thetimeAlignmentTimer associated with this TAG. Otherwise, if thetimeAlignmentTimer associated with this TAG is not running, the TimingAdvance Command for this TAG may be applied and the timeAlignmentTimerassociated with this TAG started. When the contention resolution isconsidered not successful, a timeAlignmentTimer associated with this TAGmay be stopped. Otherwise, the MAC entity may ignore the received TimingAdvance Command.

In example embodiments, a timer is running once it is started, until itis stopped or until it expires; otherwise it may not be running. A timercan be started if it is not running or restarted if it is running. Forexample, a timer may be started or restarted from its initial value.

Example embodiments of the disclosure may enable operation ofmulti-carrier communications. Other example embodiments may comprise anon-transitory tangible computer readable media comprising instructionsexecutable by one or more processors to cause operation of multi-carriercommunications. Yet other example embodiments may comprise an article ofmanufacture that comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g. wirelesscommunicator, UE, base station, etc.) to enable operation ofmulti-carrier communications. The device may include processors, memory,interfaces, and/or the like. Other example embodiments may comprisecommunication networks comprising devices such as base stations,wireless devices (or user equipment: UE), servers, switches, antennas,and/or the like.

In an example, the MAC entity may be configured with one or more SCells.In an example, the network may activate and/or deactivate the configuredSCells. The SpCell may always be activated. The network may activate anddeactivates the SCell(s) by sending the Activation/Deactivation MACcontrol element. The MAC entity may maintain a sCellDeactivationTimertimer for a configured SCell. Upon the expiry of sCellDeactivationTimertimer, the MAC entity may deactivate the associated SCell. In anexample, the same initial timer value may apply to each instance of thesCellDeactivationTimer and it may be configured by RRC. The configuredSCells may initially be deactivated upon addition and after a handover.The configured SCG SCells may initially be deactivated after a SCGchange.

In an example, if the MAC entity receives an Activation/Deactivation MACcontrol element in a TTI activating a SCell, the MAC entity may, in aTTI according to the timing defined below, activate the SCell and applynormal SCell operation including SRS transmissions on the SCell,CQI/PMI/RI/PTI/CRI reporting for the SCell, PDCCH monitoring on theSCell, PDCCH monitoring for the SCell and PUCCH transmissions on theSCell, if configured. The MAC entity may start or restart thesCellDeactivationTimer associated with the SCell and trigger powerheadroom report (PHR). In an example, if the MAC entity receives anActivation/Deactivation MAC control element in a TTI deactivating aSCell or if the sCellDeactivationTimer associated with an activatedSCell expires in the TTI, the MAC entity may, in a TTI according to thetiming defined below, deactivate the SCell, stop thesCellDeactivationTimer associated with the SCell and flush all HARQbuffers associated with the SCell.

In an example, when a UE receives an activation command for a secondarycell in subframe n, the corresponding actions above may be applied nolater than the minimum requirements and no earlier than subframe n+8,except for the actions related to CSI reporting on a serving cell whichmay be active in subframe n+8 and the actions related to thesCellDeactivationTimer associated with the secondary cell which may beapplied in subframe n+8. The actions related to CSI reporting on aserving cell which is not active in subframe n+8 may be applied in theearliest subframe after n+8 in which the serving cell is active.

In an example, when a UE receives a deactivation command for a secondarycell or the sCellDeactivationTimer associated with the secondary cellexpires in subframe n, the corresponding actions above may apply nolater than the minimum requirement except for the actions related to CSIreporting on a serving cell which is active which may be applied insubframe n+8.

In an example, if the PDCCH on the activated SCell indicates an uplinkgrant or downlink assignment or if the PDCCH on the Serving Cellscheduling an activated SCell indicates an uplink grant or a downlinkassignment for the activated SCell, the MAC entity may restart thesCellDeactivationTimer associated with the SCell.

In an example, if a SCell is deactivated, the UE may not transmit SRS onthe SCell, may not report CQI/PMI/RI/PTI/CRI for the SCell, may nottransmit on UL-SCH on the SCell, may not transmit on RACH on the SCell,may not monitor the PDCCH on the SCell, may not monitor the PDCCH forthe SCell and may not transmit PUCCH on the SCell.

In an example, the HARQ feedback for the MAC PDU containingActivation/Deactivation MAC control element may not be impacted by PCellinterruption due to SCell activation/deactivation. In an example, whenSCell is deactivated, the ongoing Random Access procedure on the SCell,if any, may be aborted.

In an example, the Activation/Deactivation MAC control element of oneoctet may be identified by a MAC PDU subheader with LCID 11000. FIG. 10shows example Activation/Deactivation MAC control elements. TheActivation/Deactivation MAC control element may have a fixed size andmay consist of a single octet containing seven C-fields and one R-field.Example Activation/Deactivation MAC control element with one octet isshown in FIG. 10. The Activation/Deactivation MAC control element mayhave a fixed size and may consist of four octets containing 31 C-fieldsand one R-field. Example Activation/Deactivation MAC control element offour octets is shown in FIG. 10. In an example, for the case with noserving cell with a serving cell index (ServCellIndex) larger than 7,Activation/Deactivation MAC control element of one octet may be applied,otherwise Activation/Deactivation MAC control element of four octets maybe applied. The fields in an Activation/Deactivation MAC control elementmay be interpreted as follows. Ci: if there is an SCell configured withSCellIndex i, this field may indicate the activation/deactivation statusof the SCell with SCellIndex i, else the MAC entity may ignore the Cifield. The Ci field may be set to “1” to indicate that the SCell withSCellIndex i is activated. The Ci field is set to “0” to indicate thatthe SCell with SCellIndex i is deactivated. R: Reserved bit, set to “0”.

A base station may provide a periodic resource allocation. In a periodicresource allocation, an RRC message and/or a DCI may activate or releasea periodic resource allocation. The UE may be allocated in downlinkand/or uplink periodic radio resources without the need for transmissionof additional grants by the base station. The periodic resourceallocation may remain activated until it is released. The periodicresource allocation for example, may be called, semi-persistentscheduling or grant-free scheduling, or periodic multi-subframescheduling, and/or the like. In this specification, the example termsemi-persistent scheduling is mostly used, but other terms may also beequally used to refer to periodic resource allocation, e.g. grant-freescheduling. An example periodic resource allocation activation andrelease is shown in FIG. 12.

In the downlink, a base station may dynamically allocate resources (PRBsand MCS) to UEs at a TTI via the C-RNTI on PDCCH(s). A UE may monitorthe PDCCH(s) in order to find possible allocation when its downlinkreception is enabled (e.g. activity governed by DRX when configured).When CA is configured, the same C-RNTI applies to serving cells. Basestation may also allocate semi-persistent downlink resources for thefirst HARQ transmissions to UEs. In an example, an RRC message mayindicate the periodicity of the semi-persistent downlink grant. In anexample, a PDCCH DCI may indicate whether the downlink grant is asemi-persistent one e.g. whether it can be implicitly reused in thefollowing TTIs according to the periodicity defined by RRC.

In an example, when required, retransmissions may be explicitly signaledvia the PDCCH(s). In the sub-frames where the UE has semi-persistentdownlink resource, if the UE cannot find its C-RNTI on the PDCCH(s), adownlink transmission according to the semi-persistent allocation thatthe UE has been assigned in the TTI is assumed. Otherwise, in thesub-frames where the UE has semi-persistent downlink resource, if the UEfinds its C-RNTI on the PDCCH(s), the PDCCH allocation may override thesemi-persistent allocation for that TTI and the UE may not decode thesemi-persistent resources.

When CA is configured, semi-persistent downlink resources may beconfigured for the PCell and/or SCell(s). In an example, PDCCH dynamicallocations for the PCell and/or SCell(s) may override thesemi-persistent allocation.

In the uplink, a base station may dynamically allocate resources (PRBsand MCS) to UEs at a TTI via the C-RNTI on PDCCH(s). A UE may monitorthe PDCCH(s) in order to find possible allocation for uplinktransmission when its downlink reception is enabled (activity governedby DRX when configured). When CA is configured, the same C-RNTI appliesto serving cells. In addition, a base station may allocate asemi-persistent uplink resource for the first HARQ transmissions andpotentially retransmissions to UEs. In an example, an RRC may define theperiodicity of the semi-persistent uplink grant. PDCCH may indicatewhether the uplink grant is a semi-persistent one e.g. whether it can beimplicitly reused in the following TTIs according to the periodicitydefined by RRC.

In an example, in the sub-frames where the UE has semi-persistent uplinkresource, if the UE cannot find its C-RNTI on the PDCCH(s), an uplinktransmission according to the semi-persistent allocation that the UE hasbeen assigned in the TTI may be made. The network may perform decodingof the pre-defined PRBs according to the pre-defined MCS. Otherwise, inthe sub-frames where the UE has semi-persistent uplink resource, if theUE finds its C-RNTI on the PDCCH(s), the PDCCH allocation may overridethe persistent allocation for that TTI and the UE's transmission followsthe PDCCH allocation, not the semi-persistent allocation.Retransmissions may be either implicitly allocated in which case the UEuses the semi-persistent uplink allocation, or explicitly allocated viaPDCCH(s) in which case the UE does not follow the semi-persistentallocation.

Vehicular communication services, represented by V2X services, maycomprise of the following different types: V2V, V21, V2N and/or V2P. V2Xservices may be provided by PC5 interface (sidelink) and/or Uu interface(UE to base station interface). Support of V2X services via PC5interface may be provided by V2X sidelink communication, which is a modeof communication whereby UEs may communicate with each other directlyover the PC5 interface. This communication mode may be supported whenthe UE is served by E-UTRAN and when the UE is outside of E-UTRAcoverage. The UEs authorized to be used for V2X services may perform V2Xsidelink communication.

The user plane protocol stack and functions for sidelink communicationmay be used for V2X sidelink communication. In order to assist the eNBto provide sidelink resources, the UE in RRC_CONNECTED may reportgeographical location information to the eNB. The eNB may configure theUE to report the complete UE geographical location information based onperiodic reporting via the existing measurement report signaling.

In an example, for V2X communication, k SPS (e.g. k=8 or 16, etc)configurations with different parameters may be configured by eNB andSPS configurations may be active at the same time. Theactivation/deactivation of an SPS configuration may signaled via a PDCCHDCI and/or an RRC message by eNB. The logical channel prioritization forUu may be used.

For V2X communication, a UE may provide UE assistance information to aneNB. Reporting of UE assistance information may be configured by eNBtransmitting one or more RRC messages. The UE assistance information mayinclude parameters related to the SPS configuration. Triggering of UEassistance information transmission may be left to UE implementation.For instance, the UE may be allowed to report the UE assistanceinformation when change in estimated periodicity and/or timing offset ofpacket arrival occurs. For V2X communication via Uu, SR mask as perlegacy mechanism may be used.

In an example, for unicast transmission of V2X messages, the V2X messagemay be delivered via Non-GBR bearers as well as GBR bearers. In order tomeet the QoS requirement for V2X message delivery for V2X services, aNon-GBR QCI value and a GBR QCI value for V2X messages may be used. Forbroadcasting V2X messages, SC-PTM or MBSFN transmission may be used. Inorder to reduce SC-PTM/MBSFN latency, shorter (SC-)MCCH repetitionperiod for SC-PTM/MBSFN, modification period for SC-PTM/MBSFN and MCHscheduling period for MBSFN may be supported. Reception of downlinkbroadcast of V2X messages in different carriers/PLMNs may be supportedby having multiple receiver chains in the UE.

In an example embodiment, various DCI formats may be used for SPSscheduling. For example, the DCI format 0 may be used for uplink SPS. Inan example, the fields for DCI format 0 may comprise one or more of thefollowing fields: Carrier indicator e.g. 0 or 3 bits. Flag forformat0/format1A differentiation e.g. 1 bit, where value 0 may indicateformat 0 and value 1 may indicate format 1A. Frequency hopping flag,e.g. 1 bit. This field may be used as the MSB of the correspondingresource allocation field for resource allocation type 1. Resource blockassignment and hopping resource allocation, e.g. ┌log₂ (N_(RB)^(UL)(N_(RB) ^(UL)+1)/2)┐ bits where N_(RB) ^(UL) may be the uplinkbandwidth configuration in number of resource blocks. Modulation andcoding scheme and redundancy version e.g. 5 bits. New data indicatore.g. 1 bit. TPC command for scheduled PUSCH e.g. 2 bits. Cyclic shiftfor DM RS and OCC index e.g. 3 bits. UL index e.g. 2 bits (this fieldmay be present for TDD operation with uplink-downlink configuration 0).Downlink Assignment Index (DAI) e.g. 2 bits (this field may be presentfor cases with TDD primary cell and either TDD operation withuplink-downlink configurations 1-6 or FDD operation). CSI request e.g.1, 2 or 3 bits. The 2-bit field may apply to UEs configured with no morethan five DL cells and to UEs that are configured with more than one DLcell and when the corresponding DCI format is mapped onto the UEspecific search space given by the C-RNTI, UEs that are configured byhigher layers with more than one CSI process and when the correspondingDCI format is mapped onto the UE specific search space given by theC-RNTI, UEs that are configured with two CSI measurement sets by higherlayers with the parameter csi-MeasSubframeSet, and when thecorresponding DCI format is mapped onto the UE specific search spacegiven by the C-RNTI; the 3-bit field may apply to the UEs that areconfigured with more than five DL cells and when the corresponding DCIformat is mapped onto the UE specific search space given by the C-RNTI;otherwise the 1-bit field may apply. SRS request e.g. 0 or 1 bit. Thisfield may be present in DCI formats scheduling PUSCH which are mappedonto the UE specific search space given by the C-RNTI. Resourceallocation type e.g. 1 bit. This field may be present if N_(RB)^(UL)≤N_(RB) ^(UL) where N_(RB) ^(UL) may be the uplink bandwidthconfiguration in number of resource blocks and N_(RB) ^(UL) may be thedownlink bandwidth configuration in number of resource blocks. Inexample, one or more fields may be added to a DCI for SPS to enhance SPSscheduling process. In example, one or more of the fields may bereplaced with new fields, or new values, or may be interpreteddifferently for SPS to enhance SPS scheduling process.

A base station may transmit one or more RRC messages to a wirelessdevice to configure SPS. The one or more RRC messages may comprise SPSconfiguration parameters. Example SPS configuration parameters arepresented below. In example, one or more parameters may be added to anRRC message for SPS to enhance SPS scheduling process. In example, oneor more some of the parameters for an SPS in an RRC message may bereplaced with new parameters, or new values, or may be interpreteddifferently for SPS to enhance SPS scheduling process. In an example, IESPS-Config may be used by RRC to specify the semi-persistent schedulingconfiguration. In an example, the IE SPS-Config may be SEQUENCE{semiPersistSchedC-RNTI: C-RNTI; sps-ConfigDL: SPS-ConfigDL;sps-ConfigUL: SPS-ConfigUL}. SPS-ConfigDL IE may comprisesemiPersistSchedIntervalDL, numberOfConfSPS-Processes,n1PUCCH-AN-PersistentList, twoAntennaPortActivated,n1PUCCH-AN-PersistentListP1, and/or other parameters. In an example,SPS-ConfigUL IE may comprise semiPersistSchedIntervalUL,implicitReleaseAfter, p0-NominalPUSCH-Persistent,p0-UE-PUSCH-Persistent, twoIntervalsConfig, p0-PersistentSubframeSet2,p0-NominalPUSCH-PersistentSubframeSet2, p0-UE-PUSCH- and/orPersistentSubframeSet2, and/or other parameters.

In an example, one or more RRC configuration parameters may comprise oneor more of the following parameters to configure SPS for a wirelessdevice. In an example, SPS configuration may include MCS employed forpacket transmission of an MCS grant. In an example, implicitReleaseAfterIE may be the number of empty transmissions before implicit release,e.g. value e2 may corresponds to 2 transmissions, e3 may correspond to 3transmissions and so on. In an example, n1PUCCH-AN-PersistentList IE,n1PUCCH-AN-PersistentListP1 IE may be the List of parameter: n_(PUCCH)^((1,p)) for antenna port P0 and for antenna port P1 respectively. Fieldn1-PUCCH-AN-PersistentListP1 IE may be applicable if thetwoAntennaPortActivatedPUCCH-Format1a1b in PUCCH-ConfigDedicated-v1020is set to true. Otherwise the field may not be configured.

In an example, numberOfConfSPS-Processes IE may be the number ofconfigured HARQ processes for Semi-Persistent Scheduling. In an example,p0-NominalPUSCH-Persistent IE may be the parameter: P_(O_NOMINAL_PUSCH)(0) used in PUSCH power control with unit in dBm and step 1. This fieldmay be applicable for persistent scheduling. If choice setup is used andp0-Persistent is absent, the value of p0-NominalPUSCH forp0-NominalPUSCH-Persistent may be applied. If uplink power controlsubframe sets are configured by tpc-SubframeSet, this field may applyfor uplink power control subframe set 1.

In an example, p0-NominalPUSCH-PersistentSubframeSet2 IE may be theparameter: P_(O_NOMINAL_PUSCH) (0) used in PUSCH power control with unitin dBm and step 1. This field may be applicable for persistentscheduling. If p0-PersistentSubframeSet2-r12 is not configured, thevalue of p0-NominalPUSCH-SubframeSet2-r12 may be applied forp0-NominalPUSCH-PersistentSubframeSet2. E-UTRAN may configure this fieldif uplink power control subframe sets are configured by tpc-SubframeSet,in which case this field may apply for uplink power control subframe set2. In an example, p0-UE-PUSCH-Persistent IE may be the parameter:P_(O_UE_PUSCH) (0) used in PUSCH power control with unit in dB. Thisfield may be applicable for persistent scheduling. If choice setup isused and p0-Persistent is absent, the value of p0-UE-PUSCH may beapplied for p0-UE-PUSCH-Persistent. If uplink power control subframesets are configured by tpc-SubframeSet, this field may be applied foruplink power control subframe set 1. In an example,p0-UE-PUSCH-PersistentSubframeSet2 IE may be the parameter:P_(O_UE_PUSCH) (0) used in PUSCH power control with unit in dB. Thisfield may be applicable for persistent scheduling. Ifp0-PersistentSubframeSet2-r12 is not configured, the value ofp0-UE-PUSCH-SubframeSet2 may be applied forp0-UE-PUSCH-PersistentSubframeSet2. E-UTRAN may configure this field ifuplink power control subframe sets are configured by tpc-SubframeSet, inwhich case this field may apply for uplink power control subframe set 2.

In an example, semiPersistSchedC-RNTI IE may be Semi-PersistentScheduling C-RNTI. In an example, semiPersistSchedIntervalDL IE may beSemi-persistent scheduling interval in downlink. Its value may be innumber of sub-frames. Value sf10 may correspond to 10 sub-frames, sf20may correspond to 20 sub-frames and so on. For TDD, the UE may roundthis parameter down to the nearest integer (of 10 sub-frames), e.g. sf10may correspond to 10 sub-frames, sf32 may correspond to 30 sub-frames,sf128 may correspond to 120 sub-frames. In an example,semiPersistSchedIntervalUL IE may be semi-persistent scheduling intervalin uplink. Its value in number of sub-frames. Value sf10 may correspondto 10 sub-frames, sf20 may correspond to 20 sub-frames and so on. ForTDD, the UE may round this parameter down to the nearest integer (of 10sub-frames), e.g. sf10 may correspond to 10 sub-frames, sf32 maycorrespond to 30 sub-frames, sf128 may correspond to 120 sub-frames. Inan example, twoIntervalsConfig IE may be trigger oftwo-intervals-Semi-Persistent Scheduling in uplink. If this field ispresent, two-intervals-SPS is enabled for uplink. Otherwise,two-intervals-SPS is disabled.

In an example, multiple downlink or uplink SPS may be configured for acell. In an example, multiple SPS RNTIs may be configured when aplurality of SPSs is configured. A base station may transmit to a UE atleast one RRC message comprising SPS configuration parameters comprisinga first SPS RNTI and a second SPS RNTI. For example, a first SPS RNTImay be configured for a first SPS configuration (e.g. for VOIP), and asecond SPS RNTI may be configured for a second SPS configuration (e.g.for V2X communications). The UE may monitor PDCCH for at least DCIscorresponding to the first SPS RNTI and the second SPS RNTI.

When Semi-Persistent Scheduling is enabled by RRC, at least one or moreof the following information may be provided: Semi-Persistent SchedulingC-RNTI(s); Uplink Semi-Persistent Scheduling intervalsemiPersistSchedIntervalUL, number of empty transmissions beforeimplicit release implicitReleaseAfter, if Semi-Persistent Scheduling isenabled for the uplink; Whether twoIntervalsConfig is enabled ordisabled for uplink, for TDD; Downlink Semi-Persistent Schedulinginterval semiPersistSchedIntervalDL and number of configured HARQprocesses for Semi-Persistent Scheduling numberOfConfSPS-Processes, ifSemi-Persistent Scheduling is enabled for the downlink; and/or otherparameters.

When Semi-Persistent Scheduling for uplink or downlink is disabled byRRC, the corresponding configured grant or configured assignment may bediscarded.

In an example, after a Semi-Persistent downlink assignment isconfigured, the MAC entity may consider sequentially that the Nthassignment occurs in the subframe for which:(10*SFN+subframe)=[(10*SFNstart time+subframestarttime)+N*semiPersistSchedIntervalDL] modulo 10240. Where SFNstart timeand subframestart time may be the SFN and subframe, respectively, at thetime the configured downlink assignment were (re)initialized.

In an example, after a Semi-Persistent Scheduling uplink grant isconfigured, the MAC entity may: if twoIntervalsConfig is enabled byupper layer: set the Subframe_Offset according to Table below. else: setSubframe_Offset to 0. consider sequentially that the Nth grant occurs inthe subframe for which: (10*SFN+subframe)=[(10*SFNstarttime+subframestart time)+N*semiPersistSchedIntervalUL+Subframe_Offset*(Nmodulo 2)] modulo 10240. Where SFNstart time and subframestart time maybe the SFN and subframe, respectively, at the time the configured uplinkgrant were (re-)initialised. FIG. 11. shows example subframe offsetvalues.

The MAC entity may clear the configured uplink grant immediately afterimplicitReleaseAfter number of consecutive MAC PDUs containing zero MACSDUs have been provided by the Multiplexing and Assembly entity, on theSemi-Persistent Scheduling resource. Retransmissions for Semi-PersistentScheduling may continue after clearing the configured uplink grant.

In an example embodiment, SPS configurations may be enhanced to supporttransmission of various V2X traffic and/or voice traffic by a UE. Thereis a need to support multiple SPS configurations for a UE. For example,a UE supporting V2X may need to support multiple uplink SPSconfigurations for transmitting various periodic (or semi-periodic)traffic and/or voice traffic in the uplink. Other examples may beprovided. For example, CAM messages in V2X may be semi-periodic. In somescenarios, CAM message generation may be dynamic in terms of size,periodicity and timing. Such changes may result in misalignment betweenSPS timing and CAM timing. There may be some regularity in size andperiodicity between different triggers. Enhanced SPS mechanisms may bebeneficial to transmit V2X traffic, voice traffic, and/or the like. Inan example, various SPS periodicity, for example 100 ms and 1 s may beconfigured.

In an example, multiple SPS configurations may be configured for UUand/or PC5 interface. An eNB may configure multiple SPS configurationsfor a given UE. In an example, SPS configuration specific MCS (e.g. MCSas a part of the RRC SPS-configuration) and/orSPS-configuration-specific periodicity may be configured. In an example,some of the SPS configuration parameters may be the same across multipleSPS and some other SPS configuration parameters may be different acrossSPS configurations. The eNB may dynamically trigger/release thedifferent SPS-configurations employing (E)PDCCH DCIs. In an example, themultiple SPS configurations may be indicated by eNB RRC signaling. Thedynamical triggering and releasing may be performed by eNB transmitting(E)PDCCH DCI to the UE employing SPS C-RNTI.

In an example embodiment, a UE may transmit UE SPS assistant informationto a base station indicating that the UE does not intend and/or intendto transmit data before a transmission associated to an SPSconfiguration. The eNB may acknowledge the UE indication. For V2Xcommunication, a UE may provide UE assistance information to an eNB.Reporting of UE assistance information may be configured by eNBtransmitting one or more RRC messages. The UE assistance information mayinclude parameters related to the SPS configuration. Triggering of UEassistance information transmission may be left to UE implementation.For instance, the UE may be allowed to report the UE assistanceinformation when change in estimated periodicity and/or timing offset ofpacket arrival occurs. For V2X communication via Uu, SR mask as perlegacy mechanism may be used.

Some example V2X messages are CAM, DENM and BSM. For Example, CAMmessage may have the following characteristics. Content: status (e.g.time, position, motion state, activated system), attribute (data aboutdimension, vehicle type and role in the road traffic). Periodicity:typical time difference between consecutive packets generation isbounded to the [0.1, 1] sec range. Length: Variable. For Example, DENMmessage may have the following characteristics. Content: Containinformation related to a variety of events. Periodicity: Event triggersthe DENM update. In between two consequent DENM updates, it is repeatedwith a pre-defined transmission interval. Length: Fixed until DENMupdate. For Example, BSM message may have the following characteristics.Content: Part I contains some of the basic vehicle state informationsuch as the message ID, vehicle ID, vehicle latitude/longitude, speedand acceleration status. Part II contains two option data frames:VehicleSafetyExtension and VehicleStatus. Periodicity: Periodic, theperiodicity may be different considering whether BSM part II is includedor not and the different application type. Length: Fixed, with differentmessage size considering whether part II exists or not.

In an example, SPS may be employed for the transmission of BSM, DENMsand CAMs. For example, the UE's speed/position/direction changes withina range. BSM may be periodic traffic with a period of 100 ms. Themessage size of BSM may be in the range of 132˜300 Bytes withoutcertificate and 241˜409 Bytes with certificate. DENMs, once triggered,may be transmitted periodically with a given message period which mayremain unchanged. The message size of the DENM may be 200˜1200 Bytes. Ifthe UE's speed/position/direction does not change or changes within asmall range, the CAM generation periodicity may be fixed.

The SPS may be supported for the UL and DL VoIP transmission. In thecurrent SPS specification, the base station may configure SPSperiodicity via dedicated RRC signaling. The periodicity of VoIP packetis generally fixed.

The UE may transmit traffic associated with multiple V2X services, whichmay require different periodicity and packet sizes. The SPS TB size andperiod may be adapted to different V2X services. Multiple parallel SPSprocesses may be activated at the UE. The SPS processes may differ inthe amount of resource blocks (RBs) allocated and/or SPS period and maycorrespond to different types of V2X packets. Once the AS layer of UEreceives the V2X packets from upper layer, the UE may trigger V2X packettransmissions on the corresponding SPS grant. Multiple UL SPSconfigurations may be configured for the UE.

The eNB may configure different SPS C-RNTIs for different SPS processesof the UE. SPS activation and release mechanism may be implemented.Employing at least one or more SPS RNTIs, the eNB may trigger which SPSprocess is activated or released. In an example implementation, in orderto support multiple SPS configurations different SPS C-RNTIs may beconfigured for different SPS traffic types. For example, a first SPSC-RNTI may be configured for SPS configuration to transmit voicetraffic, a second SPS C-RNTI may be configured for SPS configuration totransmit a V2X traffic. An eNB may transmit one or more RRC messagescomprising multiple SPS configuration parameters. The multiple SPSconfiguration parameters may comprise multiple SPS-RNTI parameters formultiple SPS traffic types (e.g. multiple UL SPS configurations).

In an example, power-control commands may be provided simultaneously toa group of UEs on PDCCH using one or more DCI formats (e.g., DCI formats3 or 3A). In an example, an eNB may transmit DCI format 3/3A on aregular basis to adjust the PUCCH transmit power, for example, prior toperiodic uplink CSI reports. In an example, an eNB may transmit DCIformat 3/3A to adjust PUSCH transmit power of a group of UEs. In anexample, an eNB may transmit DCI format 3/3A to power controlsemi-persistently scheduled UEs. In an example, uplink transmission ofPUSCH (UL-SCH) and/or PUCCH (e.g., L1/L2 control signaling) may bewithout explicit scheduling assignments/grants.

In an example, the power-control command carried on the PDCCH with afirst DCI format (e.g., format 3) may consist of two bits, correspondingto the four different transmission power update steps of −1, 0, +1, or+3 dB. In an example, the power-control command carried on the PDCCHwith a second DCI format (e.g., format 3A) may consist of one bit,corresponding to the transmission power update steps of −1 and +1 dB.

In an example, the power-control message may be directed to a group ofUEs using an RNTI specific for the group of the UEs. A UE may beallocated two power-control RNTIs (e.g., TPC-PUSCH-RNTI and/orTPC-PUCCH-RNTI). In an example, an eNB may configure a group of UEs witha common TPC-PUSCH-RNTI for group power control of PUSCH. In an example,an eNB may configure a group of UEs with a common TPC-PUCCH-RNTI forgroup power control of PUCCH. In an example, TPC-PUSCH-RNTI and/orTPC-PUCCH-RNTI may comprise a fixed number of bits (e.g., 16 bits) andtheir value may range from 1 to a first number (e.g., 65523, e.g.,0x0001 to 0xFFF3 in hexadecimal). The power-control RNTIs may be commonto a group of UEs and a UE within the group may be informed through RRCsignaling about which bit (if UE receives PDCCH of second DCI format,e.g., 3A) or bits (if UE receives PDCCH of first DCI format, e.g., 3) inthe DCI message it should follow for power adjustment.

In an example, DCI format 3 may be used for the transmission of TPCcommands for PUCCH and PUSCH with 2-bit power adjustments. In anexample, the following information may be transmitted by means of thefirst DCI format (e.g., format 3): TPC command number 1, TPC commandnumber 2, . . . , TPC command number N where

${N = \left\lfloor \frac{L_{{format}\; 0}}{2} \right\rfloor},$and where L_(format 0) may be equal to the payload size of format 0before CRC attachment when format 0 is mapped onto the common searchspace, including any padding bits appended to format 0. In an example,the parameter tpc-Index and/or tpc-Index-PUCCH-SCell-r13 provided byhigher layers may determine the index to the TPC command for a given UE.In an example, if

${\left\lfloor \frac{L_{{format}\; 0}}{2} \right\rfloor < \frac{L_{{format}\; 0}}{2}},$a bit of value zero may be appended to format 3. In an example, forBL/CE UE, L_(format 0) and format 0 may be replaced by L_(format 6-0A)and format 6-0A, respectively, in the description above.

In an example, second DCI format (e.g., format 3A) may be used for thetransmission of TPC commands for PUCCH and PUSCH with single bit poweradjustments. In an example, the following information may be transmittedby means of the second DCI format (e.g., format 3A):

TPC command number 1, TPC command number 2, . . . , TPC command number M

where M=L_(format 0), and where L_(format 0) may be equal to the payloadsize of format 0 before CRC attachment when format 0 is mapped onto thecommon search space, including any padding bits appended to format 0.The parameter tpc-Index or tpc-Index-PUCCH-SCell-r13 provided by higherlayers determines the index to the TPC command for a given UE. In anexample, for BL/CE UE, L_(format 0) and format 0 may be replaced byL_(format 6-0A) and format 6-0A, respectively, in the description above.

In an example, δ_(PUSCH,c) may be a correction value, may be referred toas a TPC command, and may be jointly coded with other TPC commands inPDCCH/MPDCCH with DCI format 3/3A whose CRC parity bits are scrambledwith TPC-PUSCH-RNTI.

In an example, for serving cell c and a non-BL/CE UE, the UE may attemptto decode a DCI format 3/3A with the UE's TPC-PUSCH-RNTI in everysubframe except when in DRX or where serving cell c is deactivated.

In an example, the δ_(PUSCH) dB accumulated values signaled onPDCCH/MPDCCH with DCI format 3/3A may be according to one of the FIG. 13or FIG. 14 as determined by the parameter TPC-Index provided by higherlayers.

In an example, in response to a UE being configured by higher layers todecode PDCCHs with the CRC scrambled by the TPC-PUCCH-RNTI, the UE maydecode the PDCCH according to the combination defined in FIG. 15. Thenotation 3/3A may imply that the UE may receive either DCI format 3 orDCI format 3A depending on the configuration. In an example, in responseto a UE being configured by higher layers to decode MPDCCHs with the CRCscrambled by the TPC-PUCCH-RNTI, the UE may decode the MPDCCH accordingto the combination defined in FIG. 16. The notation 3/3A may imply thatthe UE may receive either DCI format 3 or DCI format 3A depending on theconfiguration. In an example, in response to a UE being configured byhigher layers to decode PDCCHs with the CRC scrambled by theTPC-PUSCH-RNTI, the UE may decode the PDCCH according to the combinationdefined in FIG. 15. The notation 3/3A may imply that the UE may receiveeither DCI format 3 or DCI format 3A depending on the configuration. Inan example, in response to a UE being configured by higher layers todecode MPDCCHs with the CRC scrambled by the TPC-PUSCH-RNTI, the UE maydecode the MPDCCH according to the combination defined in FIG. 17. Thenotation 3/3A imply that the UE may receive either DCI format 3 or DCIformat 3A depending on the configuration.

Group power control is a useful procedure to control the transmission(e.g., PUSCH and/or PUCCH transmissions) power levels of a group of UEs.In an example, group power control may be used to control PUCCHtransmission (e.g., on a primary cell and/or a secondary cell) power ofa group of UEs, for example prior to periodic CSI report. In an example,group power control may be used to control PUSCH transmissions of agroup of UEs on a primary cell. In an example, the PUSCH transmissionsof the group of UEs may correspond to semi-persistently scheduledtransmissions. In legacy group power control procedures, semi-persistentscheduling may be configured for a UE on SPCell only (e.g., primary celland/or primary secondary cell (PSCell)) and a UE may be configured witha single index (e.g., a primary index) for group power control of PUSCHon the SPCell. The legacy group power control of PUSCH is inefficientwhen performed on the secondary cell (e.g., for group power control ofsemi-persistent scheduled UEs on a secondary cell). For example, thewireless device may not determine a power control command for PUSCHtransmission on a secondary cell in response to receiving a group powercontrol. The wireless device may not determine whether a power controlcommand in a group power control DCI is directed to a primary cell or asecondary cell. There is a need to enhance the legacy group powercontrol procedures for group power control on secondary cells.

In an example embodiment, group power control DCI (e.g., DCI format 3 or3A) may be directed to a group of UEs for their PUSCH transmission on asecondary cell. In an example, group power control DCI may be directedto a group of UEs for their PUCCH transmission on a secondary cell. Inan example, the eNB may transmit a PDCCH with a group power control DCImessage on a serving cell (e.g., primary cell and/or secondary cell) forpower control of a group of UEs for their PUSCH transmission on theserving cell. The eNB may configure a UE with a tpc-PUSCH-RNTI and/or atpc-PUCCH-RNTI for group power control of PUSCH and PUCCH, respectively.The cyclic redundancy check (CRC) bits associated with the group powercontrol DCI transmitted on the PDCCH (e.g., on common search space ofthe primary cell and/or the serving cell) for PUSCH and/or PUCCH powercontrol may be scrambled with tpc-PUSCH-RNTI or tpc-PUCCH-RNTI,respectively. In an example, a UE may monitor the common search space ofa serving cell to detect PDCCH with DCI scrambled with a group powercontrol RNTI (e.g., tpc-PUSCH-RNTI and/or tpc-PUCCH-RNTI). In anexample, a UE may monitor common search space of a primary cell and/orcommon search space of a serving cell that is configured withsemi-persistent scheduling and/or common search space of a serving cellthat is configured with group power control and/or common search spaceof another serving cell to detect PDCCH with DCI scrambled with grouppower control RNTI (e.g., tpc-PUSCH-RNTI and/or tpc-PUCCH-RNTI). In anexample embodiment, a parameter TPC-Index and/or TPC-Index-PUSCH (e.g.,a primary index) may be provided by higher layers for the UE (e.g.,through RRC signaling) for group power control of PUSCH transmissions bya group of UEs on the primary cell. In an example embodiment, aparameter TPC-Index-PUSCH-SCell (e.g., a secondary index), and/or alike,may be provided by higher layers (e.g., through RRC signaling) and maybe used by the UE to determine an index to the TPC command for the UE'sPUSCH transmission on a secondary cell. An example procedure is shown inFIG. 18. In an example, the DCI may comprise a plurality of powercontrol commands. The wireless device may use the primary index (e.g.,TPC-Index-PUSCH) to determine a power control command in the pluralityof power control commands for PUSCH transmission on a primary cell. Thewireless device may use the secondary index (e.g.,TPC-Index-PUSCH-SCell) to determine a power control command in theplurality of power control commands for PUSCH transmission on thesecondary cell. In an example, the IE TPC-PDCCH-Config may be used tospecify the RNTIs and/or indexes for PUCCH and PUSCH power controlincluding PUSCH and/or PUCCH power control on a serving cell (e.g.,primary and/or secondary cell). In an example, the power controlfunction may either be setup or released with the IE. An example PDCCHconfiguration information element is shown below:

TPC-PDCCH-Config ::=  CHOICE {  release NULL,  setup SEQUENCE {  tpc-RNTI  BIT STRING (SIZE (16)),   tpc-Index  TPC-Index  } }TPC-PDCCH-ConfigSCell-r13 ::=    CHOICE {  release NULL,  setup SEQUENCE{   tpc-Index-PUCCH-SCell-r13  TPC-Index  } } TPC-PDCCH-ConfigSCell-r14::=    CHOICE {  release NULL,  setup SEQUENCE {  tpc-Index-PUSCH-SCell-r14  TPC-Index  } } TPC-Index ::=  CHOICE { indexOfFormat3   INTEGER (1..15),  indexOfFormat3A   INTEGER (1..31) }In an example, indexOfFormat3 may be the index of N in response to DCIformat 3 being used. In an example, indexOfFormat3A may be the index ofM in response to DCI format 3A being used. In an example, tpc-Index maybe the index of N or M. In an example, tpc-Index-PUCCH-SCell may beindex of N or M, where N or M may be dependent on the used DCI format(e.g., format 3 or 3A). In an example, tpc-RNTI may be the RNTI forgroup power control (e.g., using DCI format 3/3A). In an example,tpc-Index-PUSCH-SCell may be index of N or M, where N or M may bedependent on the used DCI format (e.g., format 3 or 3A). In an example,a common group power control DCI (e.g., format 3 or 3A) may be used topower control PUSCH transmission for a group of semi-persistentlyscheduled UEs on a primary and/or secondary cell.

In an example embodiment, an eNB may transmit group power control DCImessages on more than one cell. In an example, the eNB may scramble theCRC corresponding to the DCI message transmitted on a serving cell(e.g., primary cell or secondary cell) with TPC-PUSCH-RNTI for powercontrol of PUSCH transmissions of a group of UEs on the serving cell. Inan example, the eNB may scramble the CRC corresponding to the DCImessage transmitted on a serving cell (e.g., primary or secondary cell)with TPC-PUCCH-RNTI for power control of PUCCH transmissions of a groupof UEs on the serving cell. In an example, the RRC configured parametertpc-Index (for PUSCH/PUCCH power control on the primary cell) or the RRCconfigured parameter tpc-Index-PUCCH-SCell (in response to the DCI beingused for PUCCH power control on a secondary cell) or the configuredparameter (e.g., RRC configured) tpc-Index-PUSCH-SCell (in response tothe DCI being transmitted for PUSCH power control on the secondary cell)may provide an index to the TPC command in the DCI message.

In an example, a UE may be indicated, e.g., implicitly or explicitly, onand/or for which SCell(s) the UE may expect a group power control DCI(e.g., a UE may expect group power control DCI on and/or for a secondarycell that is semi-persistently scheduled). A UE may consider theindicated SCell(s) on its search for group power control DCI, e.g., theUE may limit the search for group power control DCI to the common searchspace of SCell(s) that the UE may except such DCI.

In an example embodiment, group power control DCI (e.g., DCI format 3 or3A) may be directed to a group of UEs for their PUSCH transmission on asecondary cell. In an example, group power control DCI may be directedto a group of UEs for their PUCCH transmission on a secondary cell. Inan example, the eNB may transmit a PDCCH with a group power control DCImessage on a serving cell (e.g., primary cell and/or secondary cell) forpower control of a group of UEs for their PUSCH transmission on theserving cell. The eNB may configure a UE with a tpc-PUSCH-RNTI and/or atpc-PUCCH-RNTI for group power control of PUSCH and PUCCH, respectively.The cyclic redundancy check (CRC) corresponding to the group powercontrol DCI transmitted on the PDCCH of the serving cell may bescrambled with tpc-PUSCH-RNTI or tpc-PUCCH-RNTI for PUSCH or PUCCH powercontrol, respectively. In an example, a UE may monitor the common searchspace of a serving cell to detect PDCCH with DCI scrambled with a grouppower control RNTI (e.g., tpc-PUSCH-RNTI and/or tpc-PUCCH-RNTI). In anexample, a UE may monitor common search space of a serving cell that isconfigured with semi-persistent scheduling or common search space of aserving cell that is configured with group power control to detect PDCCHwith DCI scrambled with group power control RNTI (e.g., tpc-PUSCH-RNTIand/or tpc-PUCCH-RNTI). In an example, the parameterstpc-Index-PUSCH-SCell1-r14 through tpc-Index-PUSCH-SCell31-r14 may beprovided by higher layers (e.g., through RRC signaling) and may be usedby a UE to determine the index to the TPC command for the UE's PUSCHtransmission on the corresponding secondary cell. In an example, if aUE, configured with k≤31 secondary cells, receives the group powercontrol DCI message on a secondary cell with cell index j (j≤k), the UEmay use the parameter tpc-Index-PUSCH-SCell1-r14 to determine the indexto the TPC command for the UE's PUSCH transmission on secondary cellwith cell index j. In an example, the IE TPC-PDCCH-Config may be used tospecify the RNTIs and indexes for PUCCH and PUSCH power controlincluding PUSCH and/or PUCCH power control on a serving cell (e.g.,primary and/or secondary cell). In an example, the power controlfunction may either be setup or released with the IE. An example PDCCHconfiguration information element is shown below:

TPC-PDCCH-Config ::=  CHOICE {  release NULL,  setup SEQUENCE {  tpc-RNTI  BIT STRING (SIZE (16)),   tpc-Index  TPC-Index  } }TPC-PDCCH-ConfigSCell-r13 ::=     CHOICE {  release NULL,  setupSEQUENCE {   tpc-Index-PUCCH-SCell-r13  TPC-Index  } }TPC-PDCCH-ConfigSCell-r14 ::=     CHOICE {  release NULL,  setupSEQUENCE {   tpc-Index-PUSCH-SCell1-r14  TPC-Index  tpc-Index-PUSCH-SCell2-r14  TPC-Index ...  tpc-Index-PUSCH-SCell31-r14  TPC-Index  } } TPC-Index ::=  CHOICE { indexOfFormat3   INTEGER (1..15),  index OfFormat3A   INTEGER (1..31) }

In an example, indexOfFormat3 may be the index of N in response to afirst DCI format (e.g., DCI format 3) being used. In an example,indexOfFormat3A may be the index of M in response to DCI format 3A beingused. In an example, tpc-Index may be the index of N or M. In anexample, tpc-Index-PUCCH-SCell may be index of N or M, where N or M maybe dependent on the used DCI format (e.g., format 3 or 3A). In anexample, tpc-RNTI may be the RNTI for group power control (e.g., usingDCI format 3/3A). In an example, tpc-Index-PUSCH-SCell1, . . . ,tpc-Index-PUSCH-SCell31 may be index of N or M, where N or M may bedependent on the used DCI format (e.g., format 3 or 3A). In an example,a common group power control DCI (e.g., format 3 or 3A) may be used topower control PUSCH transmission for a group of semi-persistentlyscheduled UEs on a primary and/or secondary cell. In an example, an eNBmay transmit group power control DCI messages on more than one cell. Inan example, the eNB may scramble the CRC of the DCI message transmittedon a serving cell (e.g., primary or secondary cell) with TPC-PUSCH-RNTIfor power control of PUSCH transmissions of a group of UEs on theserving cell. In an example, the eNB may scramble the CRC of the DCImessage transmitted on a serving cell (e.g., primary or secondary cell)with TPC-PUCCH-RNTI for power control of PUCCH transmissions of a groupof UEs on the serving cell. In an example, the RRC configured parametertpc-Index (e.g., for PUSCH/PUCCH power control on the primary cell) orthe RRC configured parameter tpc-Index-PUCCH-SCell (e.g., in response tothe DCI being used for PUCCH power control on a secondary cell) or theconfigured parameter (e.g., RRC configured) tpc-Index-PUSCH-SCellj(e.g., in response to the DCI being transmitted on the secondary cellwith cell index j for PUSCH power control for secondary cell with cellindex j) may provide an index to the TPC command in the DCI message.

In an example embodiment, group power control DCI (e.g., DCI format 3 or3A) may be directed to a group of UEs for their PUSCH transmission on asecondary cell. In an example, group power control DCI may be directedto a group of UEs for their PUCCH transmission on a secondary cell. Inan example, the eNB may transmit one or more PDCCH with one or moregroup power control DCI message(s) on the primary cell for power controlof a group of UEs for their PUSCH transmission on one or more servingcell(s) (e.g., primary cell and/or secondary cell). The eNB mayconfigure a UE with cell-specific tpc-PUSCH-RNTI and/or cell-specifictpc-PUCCH-RNTI for group power control of PUSCH and PUCCH, respectively.The cyclic redundancy check (CRC) bits corresponding to a group powercontrol DCI transmitted on the PDCCH of the primary cell may bescrambled with a serving cell specific tpc-PUSCH-RNTI or a serving cellspecific tpc-PUCCH-RNTI for PUSCH or PUCCH power control on the servingcell, respectively.

In an example, an IE (e.g., TPC-PDCCH-Config) may be used to specify theRNTIs and/or indexes for PUCCH and PUSCH power control including PUSCHand/or PUCCH power control on a secondary cell. The power controlfunction may either be setup or released with the IE.

TPC-PDCCH-Config ::=  CHOICE {  release NULL,  setup SEQUENCE {  tpc-RNTI  BIT STRING (SIZE (16)),   tpc-RNTI-SCell1   BIT STRING (SIZE(16)),   tpc-RNTI-SCell2   BIT STRING (SIZE (16)),   ...  tpc-RNTI-SCell31   BIT STRING (SIZE (16)),   tpc-Index  TPC-Index  } }TPC-PDCCH-ConfigSCell-r13 ::=    CHOICE {  release NULL,  setup SEQUENCE{   tpc-Index-PUCCH-SCell-r13  TPC-Index  } } TPC-Index ::=  CHOICE { indexOfFormat3   INTEGER (1..15),  indexOfFormat3A   INTEGER (1..31) }In an example, indexOfFormat3 may be the index of N when DCI format 3 isused. In an example, indexOfFormat3A may be the index of M when DCIformat 3A is used. In an example, tpc-Index may be the index of N or M.In an example, tpc-Index-PUCCH-SCell may be index of N or M, where N orM may be dependent on the used DCI format (e.g., format 3 or 3A).

In an example, tpc-RNTI may be the RNTI for scrambling the CRC of thegroup power control DCI message (e.g., using DCI format 3 or 3A) forPUSCH and/or PUCCH power control on the primary cell of a UE. In anexample, tpc-RNTI-SCell1, tpc-RNTI-SCell2, . . . , tpc-RNTI-SCell31 maybe the RNTI for scrambling the CRC for group power control DCI message(e.g., using DCI format 3 or 3A) for PUSCH and/or PUCCH power control onsecondary cells with cell index 1 (e.g., SCell₁) through secondary cellwith cell index 31 (e.g., SCell₃₁). In an example, if a UE is configuredwith k≤31 secondary cells, the eNB may use tpc-RNTI-SCellj fortransmission of a group power control DCI message for PUSCH and/or PUCCHpower control on a secondary cell with cell index j (j≤k).

In an example, a common group power control DCI message (e.g., usingformat 3 or 3A) transmitted by the eNB on the primary cell may be usedto power control PUSCH transmission for a group of semi-persistentlyscheduled UEs on a serving cell. In an example, the eNB may scramble theCRC bits associated with the DCI message with a serving cell-specificTPC-PUSCH-RNTI for power control of PUSCH transmissions of a group ofUEs on the serving cell. In an example, the eNB may scramble the CRCbits associated with the DCI message with a serving cell-specificTPC-PUCCH-RNTI for power control of PUCCH transmissions of a group ofUEs on the serving cell. In an example, the TPC-PUSCH-RNTI orTPC-PUCCH-RNTI that scrambles the CRC associated with the received DCImessage may implicitly indicate the serving cell for the UE that the DCImessage is directed to. The parameter tpc-Index may indicate the indexof a TPC command for a given UE.

In an example, a UE may be indicated, e.g., implicitly or explicitly,for which SCell(s) the UE may expect a group power control DCI (e.g., aUE may expect group power control DCI on a secondary cell that issemi-persistently scheduled). A UE may limit the search for group powercontrol DCI to SCell(s) that the UE may except such DCI. In an example,UE may search on the common search space of the primary cell for DCIwith CRC scrambled with the cell-specific RNTIs that the UE is expectingto receive group power control DCI.

In an example embodiment, group power control DCI (e.g., DCI format 3 or3A) may be directed to a group of UEs for their PUSCH transmission on asecondary cell. In an example, group power control DCI may be directedto a group of UEs for their PUCCH transmission on a secondary cell. Inan example, the eNB may transmit one or more PDCCH with one or moregroup power control DCI message(s) on the primary cell for power controlof a group of UEs for their PUSCH transmission on one or more servingcell(s) (e.g., primary cell and/or secondary cell). The eNB mayconfigure a UE with cell-specific tpc-PUSCH-RNTI and/or cell-specifictpc-PUCCH-RNTI for group power control of PUSCH and PUCCH, respectively.The cyclic redundancy check (CRC) bits associated with a group powercontrol DCI transmitted on the PDCCH of the primary cell may bescrambled with a serving cell specific tpc-PUSCH-RNTI or a serving cellspecific tpc-PUCCH-RNTI for PUSCH or PUCCH power control on the servingcell, respectively. In an example, the parametertpc-Index-PUSCH-SCell-r14 may be provided by higher layers (e.g.,through RRC signaling) and may be used by a UE to determine the index tothe TPC command for the UE's PUSCH transmission on a secondary cell.

In an example, the IE TPC-PDCCH-Config may be used to specify the RNTIsand indexes for PUCCH and PUSCH power control including PUSCH and/orPUCCH power control on a secondary cell. The power control function mayeither be setup or released with the IE.

TPC-PDCCH-Config ::=  CHOICE {  release NULL,  setup SEQUENCE {  tpc-RNTI  BIT STRING (SIZE (16)),   tpc-RNTI-SCell1   BIT STRING (SIZE(16)),   tpc-RNTI-SCell2   BIT STRING (SIZE (16)),   ...  tpc-RNTI-SCell31   BIT STRING (SIZE (16)),   tpc-Index  TPC-Index  } }TPC-PDCCH-ConfigSCell-r13 ::=    CHOICE {  release NULL,  setup SEQUENCE{   tpc-Index-PUCCH-SCell-r13  TPC-Index  } } TPC-PDCCH-ConfigSCell-r14::=    CHOICE {  release NULL,  setup SEQUENCE {  tpc-Index-PUSCH-SCell-r14  TPC-Index  } } TPC-Index ::=  CHOICE { indexOfFormat3   INTEGER (1..15),  indexOfFormat3A   INTEGER (1..31) }In an example, indexOfFormat3 may be the index of N when DCI format 3 isused. In an example, indexOfFormat3A may be the index of M when DCIformat 3A is used. In an example, tpc-Index may be the index of N or M.In an example, tpc-Index-PUCCH-SCell may be index of N or M, where N orM may be dependent on the used DCI format (e.g., format 3 or 3A).

In an example, tpc-RNTI may be the RNTI for scrambling the CRC of thegroup power control DCI message (e.g., using DCI format 3 or 3A) forPUSCH and/or PUCCH power control on the primary cell of a UE. In anexample, tpc-RNTI-SCell1, tpc-RNTI-SCell2, . . . , tpc-RNTI-SCell31 maybe the RNTI for scrambling the CRC for group power control DCI message(e.g., using DCI format 3 or 3A) for PUSCH and/or PUCCH power control onsecondary cells with cell index 1 (e.g., SCell1) through secondary cellwith cell index 31 (e.g., SCell31). In an example, if a UE configuredwith k≤31 secondary cells, the eNB may use tpc-RNTI-SCellj fortransmission of a group power control DCI message for PUSCH and/or PUCCHpower control on a secondary cell with cell index j (j≤k).

In an example, tpc-Index-PUSCH-SCell may be index of N or M, where N orM may be dependent on the used DCI format (e.g., format 3 or 3A).

In an example, a common group power control DCI message (e.g., usingformat 3 or 3A) transmitted by the eNB on the primary cell may be usedto power control PUSCH transmission for a group of semi-persistentlyscheduled UEs on a serving cell. In an example, the eNB may scramble theCRC bits associated with the DCI message with a serving cell-specificTPC-PUSCH-RNTI for power control of PUSCH transmissions of a group ofUEs on the serving cell. In an example, the eNB may scramble the CRCbits associated with the DCI message with a serving cell-specificTPC-PUCCH-RNTI for power control of PUCCH transmissions of a group ofUEs on the serving cell. In an example, the TPC-PUSCH-RNTI orTPC-PUCCH-RNTI that scrambles the CRC bits associated with the receivedDCI message may implicitly indicate the serving cell for the UE that theDCI message is directed to. In an example, the RRC configured parametertpc-Index (for PUSCH/PUCCH power control on primary cell) or the RRCconfigured parameter tpc-Index-PUCCH-SCell (for PUCCH power control on asecondary cell) or the configured parameter (e.g., RRC configured)tpc-Index-PUSCH-SCell (for PUSCH power control on a secondary cell) mayprovide an index to the TPC command in the DCI message.

In an example, a UE may be indicated, e.g., implicitly or explicitly,for which SCell(s) the UE may expect a group power control DCI (e.g., aUE may expect group power control DCI on a secondary cell that issemi-persistently scheduled). A UE may limit the search for group powercontrol DCI to SCell(s) that the UE may except such DCI. In an example,UE may search on the common search space of the primary cell for DCIwith CRC scrambled with the cell-specific RNTIs that the UE is expectingto receive group power control DCI.

In an example embodiment, group power control DCI (e.g., DCI format 3 or3A) may be directed to a group of UEs for their PUSCH transmission on asecondary cell. In an example, group power control DCI may be directedto a group of UEs for their PUCCH transmission on a secondary cell. Inan example, the eNB may transmit one or more PDCCH with one or moregroup power control DCI message(s) on the primary cell for power controlof a group of UEs for their PUSCH transmission on one or more servingcell(s) (e.g., primary cell and/or secondary cell). The eNB mayconfigure a UE with cell-specific tpc-PUSCH-RNTI and/or cell-specifictpc-PUCCH-RNTI for group power control of PUSCH and PUCCH, respectively.The cyclic redundancy check (CRC) part of a group power control DCItransmitted on the PDCCH of the primary cell may be scrambled with aserving cell specific tpc-PUSCH-RNTI or a serving cell specifictpc-PUCCH-RNTI for PUSCH or PUCCH power control on the serving cell,respectively. In an example, the parameters tpc-Index-PUSCH-SCell1-r14through tpc-Index-PUSCH-SCell31-r14 may be provided by higher layers(e.g., through RRC signaling) and may be used by a UE to determine theindex to the TPC command for the UE's PUSCH transmission on thecorresponding secondary cell. In an example, if a UE, configured withk≤31 secondary cells, receives the group power control DCI messagedirected to a secondary cell with cell index j (j≤k), the UE may use theparameter tpc-Index-PUSCH-SCellj-r14 to determine the index to the TPCcommand for the UE's PUSCH transmission on secondary cell with cellindex j.

In an example, the IE TPC-PDCCH-Config may be used to specify the RNTIsand indexes for PUCCH and PUSCH power control including PUSCH and/orPUCCH power control on a secondary cell. The power control function mayeither be setup or released with the IE.

TPC-PDCCH-Config ::=  CHOICE {  release NULL,  setup SEQUENCE {  tpc-RNTI  BIT STRING (SIZE (16)),   tpc-RNTI-SCell1   BIT STRING (SIZE(16)),   tpc-RNTI-SCell2   BIT STRING (SIZE (16)),   ...  tpc-RNTI-SCell31 BIT STRING (SIZE (16)),   tpc-Index  TPC-Index  } }TPC-PDCCH-ConfigSCell-r13 ::=    CHOICE {  release NULL,  setup SEQUENCE{   tpc-Index-PUCCH-SCell-r13  TPC-Index } } TPC-PDCCH-ConfigSCell-r14::=    CHOICE {  release NULL,  setup SEQUENCE {  tpc-Index-PUSCH-SCell1-r14  TPC-Index   tpc-Index-PUSCH-SCell2-r14 TPC-Index ...   tpc-Index-PUSCH-SCell31-r14  TPC-Index } } TPC-Index::=  CHOICE {  indexOfFormat3   INTEGER (1..15),  indexOfFormat3A  INTEGER (1..31) }In an example, indexOfFormat3 may be the index of N when DCI format 3 isused. In an example, indexOfFormat3A may be the index of M when DCIformat 3A is used. In an example, tpc-Index may be the index of N or M.In an example, tpc-Index-PUCCH-SCell may be index of N or M, where N orM may be dependent on the used DCI format (e.g., format 3 or 3A).

In an example, tpc-RNTI may be the RNTI for scrambling the CRC of thegroup power control DCI message (e.g., using DCI format 3 or 3A) forPUSCH and/or PUCCH power control on the primary cell of a UE. In anexample, tpc-RNTI-SCell1, tpc-RNTI-SCell2, . . . , tpc-RNTI-SCell31 maybe the RNTI for scrambling the CRC for group power control DCI message(e.g., using DCI format 3 or 3A) for PUSCH and/or PUCCH power control onsecondary cells with cell index 1 (e.g., SCell1) through secondary cellwith cell index 31 (e.g., SCell31). In an example, if a UE configuredwith k≤31 secondary cells, the eNB may use tpc-RNTI-SCellj fortransmission of a group power control DCI message for PUSCH and/or PUCCHpower control on a secondary cell with cell index j (j≤k). In anexample, tpc-Index-PUSCH-SCell1, . . . , tpc-Index-PUSCH-SCell31 may beindex of N or M, where N or M may be dependent on the used DCI format(e.g., format 3 or 3A).

In an example embodiment, a common group power control DCI message(e.g., using format 3 or 3A) transmitted by the eNB on the primary cellmay be used to power control PUSCH transmission for a group ofsemi-persistently scheduled UEs on a serving cell. In an example, theeNB may scramble the CRC bits associated with the DCI message with aserving cell-specific TPC-PUSCH-RNTI for power control of PUSCHtransmissions of a group of UEs on the serving cell. In an example, theeNB may scramble the CRC bits associated with the DCI message with aserving cell-specific TPC-PUCCH-RNTI for power control of PUCCHtransmissions of a group of UEs on the serving cell. In an example, theTPC-PUSCH-RNTI or TPC-PUCCH-RNTI that scrambles the CRC bits associatedwith the received DCI message may implicitly indicate the serving cellfor the UE that the DCI message is directed to. In an example, the RRCconfigured parameter tpc-Index (for PUSCH/PUCCH power control on primarycell) or the RRC configured parameter tpc-Index-PUCCH-SCell (for PUCCHpower control on a secondary cell) or the configured parameter (e.g.,RRC configured) tpc-Index-PUSCH-SCellj (for PUSCH power control on asecondary cell with cell index j) may provide an index to the TPCcommand in the DCI message.

In an example, a UE may be indicated, e.g., implicitly or explicitly,for which SCell(s) the UE may expect a group power control DCI (e.g., aUE may expect group power control DCI on a secondary cell that issemi-persistently scheduled). A UE may limit the search for group powercontrol DCI to SCell(s) that the UE may except such DCI. In an example,UE may search on the common search space of the primary cell for DCIwith CRC scrambled with the cell-specific RNTIs that the UE is expectingto receive group power control DCI.

In an example embodiment, group power control DCI (e.g., DCI format 3 or3A) may be directed to a group of UEs for their PUSCH transmission on asecondary cell. In an example, group power control DCI may be directedto a group of UEs for their PUCCH transmission on a secondary cell. Inan example, the eNB may transmit one or more PDCCH with one or moregroup power control DCI message(s) on the primary cell for power controlof a group of UEs for their PUSCH transmission on one or more servingcell(s) (e.g., primary cell and/or secondary cell). The eNB mayconfigure a UE with tpc-PUSCH-RNTI and/or tpc-PUCCH-RNTI for group powercontrol of PUSCH and PUCCH, respectively. The cyclic redundancy check(CRC) bits associated with a group power control DCI transmitted on thePDCCH of the primary cell may be scrambled with tpc-PUSCH-RNTI (or avalue derived from tpc-PUSCH-RNTI depending on a serving cell) ortpc-PUCCH-RNTI (or a value derived from tpc-PUCCH-RNTI depending on aserving cell) for PUSCH or PUCCH power control on the serving cell,respectively.

In an example, the range of values that tpc-PUSCH-RNTI or tpc-PUCCH-RNTImay take (e.g., 1 to 65523 in decimal or 0x0001 to 0xFFF3 inhexadecimal) may be partitioned among the serving cells (e.g., among theprimary cell and secondary cells or among the primary cell and activesecondary cells). In an example, the permissible range fortpc-PUSCH-RNTI or tpc-PUCCH-RNTI may be divided between the servingcells. In an example with 3 serving cells (e.g., one primary cell andtwo active secondary cells), tpc-PUSCH-RNTI or tpc-PUCCH-RNTI for PDCCHtransmitted on the primary cell may take values in the range 1 to 21841,tpc-PUSCH-RNTI or tpc-PUCCH-RNTI for PDCCH transmitted on the secondarycell with smallest cell index may take values in the range 21842 to43682, and tpc-PUSCH-RNTI or tpc-PUCCH-RNTI for PDCCH transmitted on thesecondary cell with second smallest cell index may take values in therange 43683 to 65523. In an example, the eNB may configure a UE with asingle tpc-RNTI (e.g., tpc-PUSCH-RNTI and/or TPC-PUCCH-RNTI) for primarycell and the tpc-RNTI for the secondary cells may be implicitly derivedby the UE. In an example, if the tpc-RNTI is the nth position in thepartition associated with the primary cell, the tpc-RNTI for a secondarycell is the nth position in the partition associated with the secondarycell.

In an example, the IE TPC-PDCCH-Config may be used to specify the RNTIsand indexes for PUCCH and PUSCH power control including PUSCH and/orPUCCH power control on a secondary cell. The power control function mayeither be setup or released with the IE.

TPC-PDCCH-Config ::=  CHOICE {  release NULL,  setup SEQUENCE {  tpc-RNTI  BIT STRING (SIZE (16)),   tpc-Index  TPC-Index  } }TPC-PDCCH-ConfigSCell-r13 ::=    CHOICE {  release NULL,  setup SEQUENCE{   tpc-Index-PUCCH-SCell-r13  TPC-Index  } } TPC-Index ::=  CHOICE { indexOfFormat3   INTEGER (1..15),  indexOfFormat3A   INTEGER (1..31)In an example, indexOfFormat3 may be the index of N when DCI format 3 isused. In an example, indexOfFormat3A may be the index of M when DCIformat 3A is used. In an example, tpc-Index may be the index of N or M.In an example, tpc-Index-PUCCH-SCell may be index of N or M, where N orM may be dependent on the used DCI format (e.g., format 3 or 3A). In anexample, tpc-RNTI may be the RNTI for group power control (e.g., usingDCI format 3/3A).

In an example embodiment, a common group power control DCI (e.g., format3 or 3A) transmitted by the eNB on the primary cell may be used to powercontrol PUSCH transmission of a group of semi-persistently scheduled UEson a serving cell. In an example, the eNB may scramble the CRC bitsassociated with a DCI message with TPC-PUSCH-RNTI (or a value derivedfrom TPC-PUSCH-RNTI depending on the serving cell) for power control ofPUSCH transmissions of a group of UEs on a serving cell. In an example,the eNB may scramble the CRC bits associated with a DCI message withTPC-PUCCH-RNTI (or a value derived from TPC-PUCCH-RNTI depending on theserving cell) for power control of PUCCH transmissions of a group of UEson a serving cell. In an example, the RNTI that scrambles the CRC of areceived DCI message (e.g., indicated explicitly for the primary celland derived for the secondary cells) may implicitly indicate the servingcell for the UE that the DCI message is directed to. The parametertpc-Index may indicate the index of a TPC command for a given UE.

In an example, a UE may be indicated, e.g., implicitly or explicitly,for which SCell(s) the UE may expect a group power control DCI (e.g., aUE may expect group power control DCI on a secondary cell that issemi-persistently scheduled). A UE may limit the search for group powercontrol DCI to SCell(s) that the UE may except such DCI. In an example,UE may search on the common search space of the primary cell for DCIwith CRC scrambled with the cell-specific RNTIs that the UE is expectingto receive group power control DCI.

In an example embodiment, group power control DCI (e.g., DCI format 3 or3A) may be directed to a group of UEs for their PUSCH transmission on asecondary cell. In an example, group power control DCI may be directedto a group of UEs for their PUCCH transmission on a secondary cell. Inan example, the eNB may transmit one or more PDCCH with one or moregroup power control DCI message(s) on the primary cell for power controlof a group of UEs for their PUSCH transmission on one or more servingcell(s) (e.g., primary cell and/or secondary cell). The eNB mayconfigure a UE with tpc-PUSCH-RNTI and/or tpc-PUCCH-RNTI for group powercontrol of PUSCH and PUCCH, respectively. The cyclic redundancy check(CRC) part of a group power control DCI transmitted on the PDCCH of theprimary cell may be scrambled with tpc-PUSCH-RNTI (or a value derivedfrom tpc-PUSCH-RNTI depending on a serving cell) or tpc-PUCCH-RNTI (or avalue derived from tpc-PUCCH-RNTI depending on a serving cell) for PUSCHor PUCCH power control on the serving cell, respectively. In an example,the parameter tpc-Index-PUSCH-SCell-r14 may be provided by higher layers(e.g., through RRC signaling) and may be used by a UE to determine theindex to the TPC command for the UE's PUSCH transmission on a secondarycell.

In an example, the range of values that tpc-PUSCH-RNTI or tpc-PUCCH-RNTImay take (e.g., 1 to 65523 in decimal or 0x0001 to 0xFFF3 inhexadecimal) may be partitioned among the serving cells (e.g., among theprimary cell and secondary cells or among the primary cell and activesecondary cells). In an example, the permissible range fortpc-PUSCH-RNTI or tpc-PUCCH-RNTI may be divided between the servingcells. In an example with 3 serving cells (e.g., one primary cell andtwo active secondary cells), tpc-PUSCH-RNTI or tpc-PUCCH-RNTI for PDCCHtransmitted on the primary cell may take values in the range 1 to 21841,tpc-PUSCH-RNTI or tpc-PUCCH-RNTI for PDCCH transmitted on the secondarycell with smallest cell index may take values in the range 21842 to43682, and tpc-PUSCH-RNTI or tpc-PUCCH-RNTI for PDCCH transmitted on thesecondary cell with second smallest cell index may take values in therange 43683 to 65523. In an example, the eNB may configure a UE with asingle tpc-RNTI (e.g., tpc-PUSCH-RNTI and/or TPC-PUCCH-RNTI) for primarycell and the tpc-RNTI for the secondary cells may be implicitly derivedby the UE. In an example, if the tpc-RNTI is the nth position in thepartition associated with the primary cell, the tpc-RNTI for a secondarycell is the nth position in the partition associated with the secondarycell.

In an example, the IE TPC-PDCCH-Config may be used to specify the RNTIsand indexes for PUCCH and PUSCH power control including PUSCH and/orPUCCH power control on a secondary cell. The power control function mayeither be setup or released with the IE.

TPC-PDCCH-Config ::=  CHOICE {  release NULL,  setup SEQUENCE {  tpc-RNTI  BIT STRING (SIZE (16)),   tpc-Index  TPC-Index  } }TPC-PDCCH-ConfigSCell-r13 ::=    CHOICE {  release NULL,  setup SEQUENCE{   tpc-Index-PUCCH-SCell-r13  TPC-Index  } } TPC-PDCCH-ConfigSCell-r14::=    CHOICE {  release NULL,  setup SEQUENCE {  tpc-Index-PUSCH-SCell-r14  TPC-Index  } } TPC-Index ::=  CHOICE { indexOfFormat3   INTEGER (1..15),  indexOfFormat3A   INTEGER (1..31) }In an example, indexOfFormat3 may be the index of N when DCI format 3 isused. In an example, indexOfFormat3A may be the index of M when DCIformat 3A is used. In an example, tpc-Index may be the index of N or M.In an example, tpc-Index-PUCCH-SCell may be index of N or M, where N orM may be dependent on the used DCI format (e.g., format 3 or 3A). In anexample, tpc-RNTI may be the RNTI for group power control (e.g., usingDCI format 3/3A).

In an example, a common group power control DCI message (e.g., usingformat 3 or 3A) transmitted by the eNB on the primary cell may be usedto power control PUSCH transmission of a group of semi-persistentlyscheduled UEs on a serving cell. In an example, the eNB may scramble theCRC bits associated with a DCI message with TPC-PUSCH-RNTI (or a valuederived from TPC-PUSCH-RNTI depending on the serving cell) for powercontrol of PUSCH transmissions of a group of UEs on a serving cell. Inan example, the eNB may scramble the CRC of a DCI message withTPC-PUCCH-RNTI (or a value derived from TPC-PUCCH-RNTI depending on theserving cell) for power control of PUCCH transmissions of a group of UEson a serving cell. In an example, the RNTI that scrambles the CRC of areceived DCI message (e.g., indicated explicitly for the primary celland derived for the secondary cells) may implicitly indicate the servingcell for the UE that the DCI message is directed to. In an example, theRRC configured parameter tpc-Index (for PUSCH/PUCCH power control onprimary cell) or the RRC configured parameter tpc-Index-PUCCH-SCell (forPUCCH power control on a secondary cell) or the configured parameter(e.g., RRC configured) tpc-Index-PUSCH-SCell (for PUSCH power control ona secondary cell) may provide an index to the TPC command in the DCImessage.

In an example, a UE may be indicated, e.g., implicitly or explicitly,for which SCell(s) the UE may expect a group power control DCI (e.g., aUE may expect group power control DCI on a secondary cell that issemi-persistently scheduled). A UE may limit the search for group powercontrol DCI to SCell(s) that the UE may except such DCI. In an example,UE may search on the common search space of the primary cell for DCIwith CRC scrambled with the cell-specific RNTIs that the UE is expectingto receive group power control DCI.

In an example embodiment, group power control DCI (e.g., DCI format 3 or3A) may be directed to a group of UEs for their PUSCH transmission on asecondary cell. In an example, group power control DCI may be directedto a group of UEs for their PUCCH transmission on a secondary cell. Inan example, the eNB may transmit one or more PDCCH with one or moregroup power control DCI message(s) on the primary cell for power controlof a group of UEs for their PUSCH transmission on one or more servingcell(s) (e.g., primary cell and/or secondary cell). The eNB mayconfigure a UE with tpc-PUSCH-RNTI and/or tpc-PUCCH-RNTI for group powercontrol of PUSCH and PUCCH, respectively. The cyclic redundancy check(CRC) bits associated with a group power control DCI transmitted on thePDCCH of the primary cell may be scrambled with tpc-PUSCH-RNTI (or avalue derived from tpc-PUSCH-RNTI depending on a serving cell) ortpc-PUCCH-RNTI (or a value derived from tpc-PUCCH-RNTI depending on aserving cell) for PUSCH or PUCCH power control on the serving cell,respectively. In an example, the parameters tpc-Index-PUSCH-SCell1-r14through tpc-Index-PUSCH-SCell31-r14 may be provided by higher layers(e.g., through RRC signaling) and may be used by a UE to determine theindex to the TPC command for the UE's PUSCH transmission on thecorresponding secondary cell. In an example, if a UE, configured withk≤31 secondary cells, receives the group power control DCI message on asecondary cell with cell index j (j≤k), the UE may use the parametertpc-Index-PUSCH-SCellj-r14 to determine the index to the TPC command forthe UE's PUSCH transmission on secondary cell with cell index j.

In an example, the range of values that tpc-PUSCH-RNTI or tpc-PUCCH-RNTImay take (e.g., 1 to 65523 in decimal or 0x0001 to 0xFFF3 inhexadecimal) may be partitioned among the serving cells (e.g., among theprimary cell and secondary cells or among the primary cell and activesecondary cells). In an example, the permissible range fortpc-PUSCH-RNTI or tpc-PUCCH-RNTI may be divided between the servingcells. In an example with 3 serving cells (e.g., one primary cell andtwo active secondary cells), tpc-PUSCH-RNTI or tpc-PUCCH-RNTI for PDCCHtransmitted on the primary cell may take values in the range 1 to 21841,tpc-PUSCH-RNTI or tpc-PUCCH-RNTI for PDCCH transmitted on the secondarycell with smallest cell index may take values in the range 21842 to43682, and tpc-PUSCH-RNTI or tpc-PUCCH-RNTI for PDCCH transmitted on thesecondary cell with second smallest cell index may take values in therange 43683 to 65523. In an example, the eNB may configure a UE with asingle tpc-RNTI (e.g., tpc-PUSCH-RNTI and/or TPC-PUCCH-RNTI) for primarycell and the tpc-RNTI for the secondary cells may be implicitly derivedby the UE. In an example, if the tpc-RNTI is the nth position in thepartition associated with the primary cell, the tpc-RNTI for a secondarycell is the nth position in the partition associated with the secondarycell.

In an example, the IE TPC-PDCCH-Config may be used to specify the RNTIsand indexes for PUCCH and PUSCH power control including PUSCH and/orPUCCH power control on a secondary cell. The power control function mayeither be setup or released with the IE.

TPC-PDCCH-Config ::=  CHOICE {  release NULL,  setup SEQUENCE {  tpc-RNTI  BIT STRING (SIZE (16)),   tpc-Index  TPC-Index  } }TPC-PDCCH-ConfigSCell-r13 ::=    CHOICE {  release NULL,  setup SEQUENCE{   tpc-Index-PUCCH-SCell-r13  TPC-Index  } } TPC-PDCCH-ConfigSCell-r14::=    CHOICE {  release NULL,  setup SEQUENCE {  tpc-Index-PUSCH-SCell1-r14  TPC-Index   tpc-Index-PUSCH-SCell2-r14 TPC-Index ...  } } TPC-Index ::=  CHOICE {  indexOfFormat3   INTEGER(1..15),  indexOfFormat3A   INTEGER (1..31) }In an example, indexOfFormat3 may be the index of N when DCI format 3 isused. In an example, indexOfFormat3A may be the index of M when DCIformat 3A is used. In an example, tpc-Index may be the index of N or M.In an example, tpc-Index-PUCCH-SCell may be index of N or M, where N orM may be dependent on the used DCI format (e.g., format 3 or 3A). In anexample, tpc-RNTI may be the RNTI for group power control (e.g., usingDCI format 3/3A). In an example, tpc-Index-PUSCH-SCell1, . . . ,tpc-Index-PUSCH-SCell31 may be index of N or M, where N or M may bedependent on the used DCI format (e.g., format 3 or 3A).

In an example embodiment, a common group power control DCI message(e.g., using format 3 or 3A) transmitted by the eNB on the primary cellmay be used to power control PUSCH transmission of a group ofsemi-persistently scheduled UEs on a serving cell. In an example, theeNB may scramble the CRC bits associated with a DCI message withTPC-PUSCH-RNTI (or a value derived from TPC-PUSCH-RNTI depending on theserving cell) for power control of PUSCH transmissions of a group of UEson a serving cell. In an example, the eNB may scramble the CRC bitsassociated with a DCI message with TPC-PUCCH-RNTI (or a value derivedfrom TPC-PUCCH-RNTI depending on the serving cell) for power control ofPUCCH transmissions of a group of UEs on a serving cell. In an example,the RNTI that scrambles the CRC bits associated with a received DCImessage (e.g., indicated explicitly for the primary cell and derived forthe secondary cells) may implicitly indicate the serving cell for the UEthat the DCI message is directed to. In an example, the RRC configuredparameter tpc-Index (for PUSCH/PUCCH power control on primary cell) orthe RRC configured parameter tpc-Index-PUCCH-SCell (for PUCCH powercontrol on a secondary cell) or the configured parameter (e.g., RRCconfigured) tpc-Index-PUSCH-SCellj (for PUSCH power control on asecondary cell with cell index j) may provide an index to the TPCcommand in the DCI message.

In an example, a UE may be indicated, e.g., implicitly or explicitly,for which SCell(s) the UE may expect a group power control DCI (e.g., aUE may expect group power control DCI on a secondary cell that issemi-persistently scheduled). A UE may limit the search for group powercontrol DCI to SCell(s) that the UE may except such DCI. In an example,UE may search on the common search space of the primary cell for DCIwith CRC scrambled with the cell-specific RNTIs that the UE is expectingto receive group power control DCI.

In an example embodiment, a group power control DCI (e.g., DCI format 3or 3A) may be directed to a group of UEs for their PUSCH transmission onone or more serving cells. In an example, a group power control DCI(e.g., DCI format 3 or 3A) may be directed to a group of UEs for theirPUCCH transmission on one or more serving cell(s). In an example, theeNB may transmit a PDCCH with a group power control DCI on the primarycell for group power control of a group of UEs for their PUSCHtransmission on one or more serving cells. The eNB may configure a UEwith tpc-PUSCH-RNTI and/or tpc-PUCCH-RNTI for group power control ofPUSCH and PUCCH, respectively. The cyclic redundancy check (CRC) bitsassociated with a group power control DCI transmitted on the PDCCH ofthe primary cell may be scrambled with tpc-PUSCH-RNTI or tpc-PUCCH-RNTIfor PUSCH or PUCCH power control on or more serving cell(s),respectively. In an example, the parameter tpc-Index-PUSCH-SCell-r14 maybe provided by higher layers (e.g., through RRC signaling) and may beused by a UE to determine the index to the TPC command for the UE'sPUSCH transmission on a secondary cell.

In an example, the IE TPC-PDCCH-Config may be used to specify the RNTIsand indexes for PUCCH and PUSCH power control including PUSCH and/orPUCCH power control on a secondary cell. The power control function mayeither be setup or released with the IE.

TPC-PDCCH-Config ::=  CHOICE {  release NULL,  setup SEQUENCE {  tpc-RNTI  BIT STRING (SIZE (16)),   tpc-Index  TPC-Index  } }TPC-PDCCH-ConfigSCell-r13 ::=    CHOICE {  release NULL,  setup SEQUENCE{   tpc-Index-PUCCH-SCell-r13  TPC-Index  } } TPC-PDCCH-ConfigSCell-r14::=    CHOICE {  release NULL,  setup SEQUENCE {  tpc-Index-PUSCH-SCell-r14  TPC-Index  } } TPC-Index ::=  CHOICE { indexOfFormat3   INTEGER (1..15),  indexOfFormat3A   INTEGER (1..31) }In an example, indexOfFormat3 may be the index of N when DCI format 3 isused. In an example, indexOfFormat3A may be the index of M when DCIformat 3A is used. In an example, tpc-Index may be the index of N or M.In an example, tpc-Index-PUCCH-SCell may be index of N or M, where N orM may be dependent on the used DCI format (e.g., format 3 or 3A). In anexample, tpc-RNTI may be the RNTI for group power control (e.g., usingDCI format 3/3A). In an example, tpc-Index-PUSCH-SCell may be index of Nor M, where N or M may be dependent on the used DCI format (e.g., format3 or 3A).

In an example embodiment, a common group power control DCI (e.g., format3 or 3A) transmitted by the eNB on the primary cell may be used to powercontrol PUSCH transmission of a group of semi-persistently scheduled UEson one or more serving cell(s). In an example, the eNB may scramble theCRC of a DCI message with TPC-PUSCH-RNTI for power control of PUSCHtransmissions of a group of UEs on one or more serving cell(s). In anexample, the eNB may scramble the CRC of a DCI message withTPC-PUCCH-RNTI for power control of PUCCH transmissions of a group ofUEs on one or more serving cell(s). In an example, the RRC configuredparameter tpc-Index (for PUSCH/PUCCH power control on the primary cell)or the RRC configured parameter tpc-Index-PUCCH-SCell (for PUCCH powercontrol on a secondary cell) or the configured parameter (e.g., RRCconfigured) tpc-Index-PUSCH-SCell (for PUSCH power control on thesecondary cell) may provide an index to the TPC command in the DCImessage.

In an example embodiment, a group power control DCI (e.g., DCI format 3or 3A) may be directed to a group of UEs for their PUSCH transmission onone or more serving cells. In an example, a group power control DCI(e.g., DCI format 3 or 3A) may be directed to a group of UEs for theirPUCCH transmission on one or more serving cell(s). In an example, theeNB may transmit a PDCCH with a group power control DCI on the primarycell for group power control of a group of UEs for their PUSCHtransmission on one or more serving cells. The eNB may configure a UEwith tpc-PUSCH-RNTI and/or tpc-PUCCH-RNTI for group power control ofPUSCH and PUCCH, respectively. The cyclic redundancy check (CRC) bitsassociated with a group power control DCI transmitted on the PDCCH ofthe primary cell may be scrambled with tpc-PUSCH-RNTI or tpc-PUCCH-RNTIfor PUSCH or PUCCH power control on or more serving cell(s),respectively. In an example, the parameters tpc-Index-PUSCH-SCell1-r14through tpc-Index-PUSCH-SCell31-r14 may be provided by higher layers(e.g., through RRC signaling) and may be used by a UE to determine theindex to the TPC command for the UE's PUSCH transmission on thecorresponding secondary cell. In an example, if a UE, configured withk≤31 secondary cells, the UE may use the parametertpc-Index-PUSCH-SCellj-r14 to determine the index to the TPC command forthe UE's PUSCH transmission on secondary cell with cell index j. In anexample, the eNB may configure a UE with tpc-Index-PUSCH-SCell for asubset of its active secondary cells (e.g. the cell with SPSconfiguration) that may be group power controlled.

In an example, the IE TPC-PDCCH-Config may be used to specify the RNTIsand indexes for PUCCH and PUSCH power control including PUSCH and/orPUCCH power control on a secondary cell. The power control function mayeither be setup or released with the IE.

TPC-PDCCH-Config ::=  CHOICE {  release NULL,  setup SEQUENCE {  tpc-RNTI  BIT STRING (SIZE (16)),   tpc-Index  TPC-Index  } }TPC-PDCCH-ConfigSCell-r13 ::=    CHOICE {  release NULL,  setup SEQUENCE{   tpc-Index-PUCCH-SCell-r13  TPC-Index  } } TPC-PDCCH-ConfigSCell-r14::=    CHOICE {  release NULL,  setup SEQUENCE {  tpc-Index-PUSCH-SCell1-r14  TPC-Index   tpc-Index-PUSCH-SCell2-r14 TPC-Index ...   tpc-Index-PUSCH-SCell31-r14  TPC-Index  } } TPC-Index::=  CHOICE {  indexOfFormat3   INTEGER (1..15),  indexOfFormat3A  INTEGER (1..31) }In an example, indexOfFormat3 may be the index of N when DCI format 3 isused. In an example, indexOfFormat3A may be the index of M when DCIformat 3A is used. In an example, tpc-Index may be the index of N or M.In an example, tpc-Index-PUCCH-SCell may be index of N or M, where N orM may be dependent on the used DCI format (e.g., format 3 or 3A). In anexample, tpc-RNTI may be the RNTI for group power control (e.g., usingDCI format 3/3A). In an example, tpc-Index-PUSCH-SCell1, . . . ,tpc-Index-PUSCH-SCell31 may be index of N or M, where N or M may bedependent on the used DCI format (e.g., format 3 or 3A).

In an example, a common group power control DCI (e.g., format 3 or 3A)transmitted by the eNB on the primary cell may be used to power controlPUSCH transmission of a group of semi-persistently scheduled UEs on oneor more serving cell(s). In an example, the eNB may scramble the CRCbits associated with a DCI message with TPC-PUSCH-RNTI for power controlof PUSCH transmissions of a group of UEs on one or more serving cell(s).In an example, the eNB may scramble the CRC bits associated with a DCImessage with TPC-PUCCH-RNTI for power control of PUCCH transmissions ofa group of UEs on one or more serving cell(s). In an example, the RRCconfigured parameter tpc-Index (for PUSCH/PUCCH power control on theprimary cell) or the RRC configured parameter tpc-Index-PUCCH-SCell (forPUCCH power control on a secondary cell) or the configured parameter(e.g., RRC configured) tpc-Index-PUSCH-SCellj (for PUSCH power controlon the secondary cell with cell index j) may provide an index to the TPCcommand in the DCI message.

According to various embodiments, a device (such as, for example, awireless device, off-network wireless device, a base station, and/or thelike), may comprise one or more processors and memory. The memory maystore instructions that, when executed by the one or more processors,cause the device to perform a series of actions. Embodiments of exampleactions are illustrated in the accompanying figures and specification.Features from various embodiments may be combined to create yet furtherembodiments.

FIG. 19 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 1910, a wireless device may receive one ormore messages. The one or more messages may comprise configurationparameters for a plurality of cells comprising a primary cell and asecondary cell. The configuration parameters may comprise: a transmitpower control (TPC) radio network temporary identifier (RNTI), a primaryTPC index for a first physical uplink shared channel (PUSCH) of theprimary cell, a secondary TPC index for a second PUSCH of the secondarycell, and periodic resource allocation configuration parametersconfiguring a periodic resource allocation for the secondary cell. At1920, a first downlink control information (DCI) may be received. TheDCI may indicate activation of the periodic resource allocation. Acommon search space for a second DCI associated with the TPC RNTI may bemonitored at 1930. The second DCI may comprise a sequence of TPCcommands. The secondary TPC index may identify a TPC command in thesequence. At 140, one or more transport blocks may be transmitted by thewireless device employing one or more transmission parameters in thefirst DCI and the TPC command.

According to an embodiment, the periodic resource allocation maycomprise semi-persistent scheduling. According to an embodiment, thecommon search space may be on the primary cell. According to anembodiment, the common search space may be on the secondary cell.According to an embodiment, the wireless device may further receive amessage indicating whether the wireless device is expected to monitorthe common search space on the secondary cell. According to anembodiment, the second DCI may have a first format or a second format.According to an embodiment, the TPC command may comprise two bits inresponse to the second DCI having the first format, otherwise the TPCcommand comprises a single bit. According to an embodiment, the two bitsmay represent minus one decibel (dB), zero dB, plus one dB or three dBand the single bit represents minus one dB or plus one dB. According toan embodiment, the configuration parameters further comprise a secondTPC RNTI. According to an embodiment, the first format is 3 and thesecond format is 3A.

FIG. 20 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2010, a wireless device may receive one ormore messages. The one or more messages may comprise configurationparameters for a plurality of cells comprising a secondary cell, theconfiguration parameters for the secondary cell comprising a radionetwork temporary identifier (RNTI) and an index. At 2020, the wirelessdevice may monitor/search a common search space of a downlink controlchannel. At 2030, a downlink control information (DCI) corresponding tothe RNTI may be received. At 2040, a determination may be made, based onthe DCI and the index, of a power control command for a physical uplinkshared channel (PUSCH) transmission on the secondary cell. At 2050, thewireless device may receive an uplink grant comprising transmissionparameters for one or more transport blocks (TBs) via the secondarycell. At 2060, the wireless device may transmit the power controlcommand by the one or more TBs employing the transmission parameters.

In this specification, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” In this specification,the term “may” is to be interpreted as “may, for example.” In otherwords, the term “may” is indicative that the phrase following the term“may” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={call, cell2}are: {cell1}, {cell2}, and {cell1, cell2}.

In this specification, parameters (Information elements: IEs) maycomprise one or more objects, and each of those objects may comprise oneor more other objects. For example, if parameter (IE) N comprisesparameter (IE) M, and parameter (IE) M comprises parameter (IE) K, andparameter (IE) K comprises parameter (information element) J, then, forexample, N comprises K, and N comprises J. In an example embodiment,when one or more messages comprise a plurality of parameters, it impliesthat a parameter in the plurality of parameters is in at least one ofthe one or more messages, but does not have to be in each of the one ormore messages. In an example, an IE may be a sequence of firstparameters (first IEs). The sequence may comprise one or more firstparameters. For example, a sequence may have a length max_length (e.g.1, 2, 3, etc). A first parameter in the sequence may be identified bythe parameter index in the sequence. The sequence may be ordered.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e hardware with a biological element) or acombination thereof, all of which are behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, Matlab or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers and microprocessors are programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDsare often programmed using hardware description languages (HDL) such asVHSIC hardware description language (VHDL) or Verilog that configureconnections between internal hardware modules with lesser functionalityon a programmable device. Finally, it needs to be emphasized that theabove-mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the spirit and scope. In fact, after reading theabove description, it will be apparent to one skilled in the relevantart(s) how to implement alternative embodiments. Thus, the presentembodiments should not be limited by any of the above describedexemplary embodiments. In particular, it should be noted that, forexample purposes, the above explanation has focused on the example(s)using LAA communication systems. However, one skilled in the art willrecognize that embodiments of the disclosure may also be implemented ina system comprising one or more TDD cells (e.g. frame structure 2 and/orframe structure 1). The disclosed methods and systems may be implementedin wireless or wireline systems. The features of various embodimentspresented in this disclosure may be combined. One or many features(method or system) of one embodiment may be implemented in otherembodiments. Only a limited number of example combinations are shown toindicate to one skilled in the art the possibility of features that maybe combined in various embodiments to create enhanced transmission andreception systems and methods.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice, one or more messages comprising configuration parameters for aplurality of cells comprising a primary cell and a secondary cell,wherein the configuration parameters comprise: a transmit power control(TPC) radio network temporary identifier (RNTI); a primary TPC index fora first physical uplink shared channel (PUSCH) of the primary cell; asecondary TPC index for a second PUSCH of the secondary cell; andperiodic resource allocation configuration parameters configuring aperiodic resource allocation for transmission of transport blocks viathe second PUSCH of the secondary cell; receiving first downlink controlinformation (DCI) indicating activation of the periodic resourceallocation for transmission of transport blocks via the second PUSCH ofthe secondary cell; monitoring a common search space for a-second DCIassociated with the TPC RNTI, wherein the second DCI comprises asequence of TPC commands, and wherein the secondary TPC index indicatesa TPC command in the sequence; and transmitting, via the second PUSCHand based on the first DCI and the TPC command, one or more transportblocks.
 2. The method of claim 1, wherein the periodic resourceallocation is semi-persistent scheduling.
 3. The method of claim 1,wherein the common search space is on the primary cell or on thesecondary cell.
 4. The method of claim 3, further comprising receiving amessage indicating whether the wireless device is expected to monitorthe common search space.
 5. The method of claim 1, wherein a format ofthe second DCI is DCI format 3 or DCI format 3A.
 6. The method of claim1, wherein the TPC command comprises two bits based on the second DCIbeing DCI format 3, and wherein the TPC command comprises a single bitbased on the second DCI being DCI format 3A.
 7. The method of claim 6,wherein the two bits represent minus one decibel (dB), zero dB, plus onedB, or three dB, and wherein the single bit represents minus one dB orplus one dB.
 8. The method of claim 1, wherein the configurationparameters further comprise a second TPC RNTI.
 9. A wireless devicecomprising: one or more processors; and memory storing instructionsthat, when executed by the one or more processors, cause the wirelessdevice to: receive one or more messages comprising configurationparameters for a plurality of cells comprising a primary cell and asecondary cell, wherein the configuration parameters comprise: atransmit power control (TPC) radio network temporary identifier (RNTI);a primary TPC index for a first physical uplink shared channel (PUSCH)of the primary cell; a secondary TPC index for a second PUSCH of thesecondary cell; and periodic resource allocation configurationparameters configuring a periodic resource allocation for transmissionof transport blocks via the second PUSCH of the secondary cell; andreceive first downlink control information (DCI) indicating activationof the periodic resource allocation for transmission of transport blocksvia the second PUSCH of the secondary cell; monitor a common searchspace for a-second DCI associated with the TPC RNTI, wherein the secondDCI comprises a sequence of TPC commands, and wherein the secondary TPCindex indicates a TPC command in the sequence; and transmit, via thesecond PUSCH and based on the first DCI and the TPC command, one or moretransport blocks.
 10. The wireless device of claim 9, wherein theperiodic resource allocation is semi-persistent scheduling.
 11. Thewireless device of claim 9, wherein the common search space is on theprimary cell or on the secondary cell.
 12. The wireless device of claim11, wherein the instructions, when executed, further cause the wirelessdevice to receive a message indicating whether the wireless device isexpected to monitor the common search space.
 13. The wireless device ofclaim 9, wherein a format of the second DCI is DCI format 3 or DCIformat 3A.
 14. The wireless device of claim 9, wherein the TPC commandcomprises two bits based on the second DCI being DCI format 3, andwherein the TPC command comprises a single bit based on the second DCIbeing DCI format 3A.
 15. The wireless device of claim 14, wherein thetwo bits represent minus one decibel (dB), zero dB, plus one dB, orthree dB, and wherein the single bit represents minus one dB or plus onedB.
 16. The wireless device of claim 9, wherein the configurationparameters further comprise a second TPC RNTI.
 17. A system comprising:a wireless device; and a base station; wherein the base station isconfigured to: send one or more messages comprising configurationparameters for a plurality of cells comprising a primary cell and asecondary cell, wherein the configuration parameters comprise: atransmit power control (TPC) radio network temporary identifier (RNTI);a primary TPC index for a first physical uplink shared channel (PUSCH)of the primary cell; a secondary TPC index for a second PUSCH of thesecondary cell; and periodic resource allocation configurationparameters configuring a periodic resource allocation for transmissionof transport blocks via the second PUSCH of the secondary cell; and sendfirst downlink control information (DCI) indicating activation of theperiodic resource allocation for transmission of transport blocks viathe second PUSCH of the secondary cell; and wherein the wireless deviceis configured to: monitor a common search space for second DCIassociated with the TPC RNTI, wherein the second DCI comprises asequence of TPC commands, and wherein the secondary TPC index indicatesa TPC command in the sequence; and send, via the second PUSCH and basedon the first DCI and the TPC command, one or more transport blocks. 18.The system of claim 17, wherein the periodic resource allocation issemi-persistent scheduling.
 19. The system of claim 17, wherein thecommon search space is on the primary cell or on the secondary cell. 20.The system of claim 19, wherein the wireless device is furtherconfigured to receive a message indicating whether the wireless deviceis expected to monitor the common search space.
 21. The system of claim17, wherein a format of the second DCI is DCI format 3 or DCI format 3A.22. The system of claim 17, wherein the TPC command comprises two bitsbased on the second DCI being DCI format 3, and wherein the TPC commandcomprises a single bit based on the second DCI being DCI format 3A. 23.The system of claim 22, wherein the two bits represent minus one decibel(dB), zero dB, plus one dB, or three dB, and wherein the single bitrepresents minus one dB or plus one dB.
 24. The system of claim 17,wherein the configuration parameters further comprise a second TPC RNTI.